🛡️ AZL-66174 — kernel

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

CVE-2025-38499 affecting package kernel for versions less than 6.6.104.2-1

In the Linux kernel, the following vulnerability has been resolved:

clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns

What we want is to verify there is that clone won't expose something

hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo"

may be a result of MNT_LOCKED on a child, but it may also come from

lacking admin rights in the userns of the namespace mount belongs to.

clone_private_mnt() checks the former, but not the latter.

There's a number of rather confusing CAP_SYS_ADMIN checks in various

userns during the mount, especially with the new mount API; they serve

different purposes and in case of clone_private_mnt() they usually,

but not always end up covering the missing check mentioned above.

Affected software

AZL-66174 is recorded against 1 package.

  • kernel (fixed in 6.6.104.2-1)

Timeline and source

Published on 11 August 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-08-11
Updated 2026-08-12
Modified 2026-04-21
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel — 6.6.104.2-1

Similar Threats

Free Vulnerability Check

Is your site affected by AZL-66174?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-66174 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.