CVE Catalog

CVE-2025-38499

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.15%

5th percentile - higher than 5% of all known CVEs

Summary

In the Linux kernel, the clone_private_mnt() function lacks a check for CAP_SYS_ADMIN in the correct user namespace. It only checks MNT_LOCKED but does not verify admin rights in the namespace the mount belongs to.

Risk Assessment

The vulnerability could allow a user without proper privileges to clone a mount that hides resources, potentially leading to privilege escalation or information disclosure.

Recommendation

Update the Linux kernel to a version containing a fix that adds a CAP_SYS_ADMIN check in the appropriate user namespace.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS