CVE-2025-38499
Last modified
CVE-2025-38499 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.4.281, < 4.5 |
| Linux | Linux Kernel | >= 4.9.280, < 4.10 |
| Linux | Linux Kernel | >= 4.14.244, < 4.15 |
| Linux | Linux Kernel | >= 4.19.204, < 4.20 |
| Linux | Linux Kernel | >= 5.4.141, < 5.5 |
| Linux | Linux Kernel | >= 5.10.59, < 5.11 |
| Linux | Linux Kernel | >= 5.13.11, < 5.14 |
| Linux | Linux Kernel | >= 5.14.1, < 5.15.190 |
| Linux | Linux Kernel | >= 5.16, < 6.1.147 |
| Linux | Linux Kernel | >= 6.2, < 6.6.100 |
| Linux | Linux Kernel | >= 6.7, < 6.12.40 |
| Linux | Linux Kernel | >= 6.13, < 6.15.3 |
| Linux | Linux Kernel | 5.14 |
| Debian | Debian Linux | 11.0 |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38499?
How severe is CVE-2025-38499?
How do I fix CVE-2025-38499?
Are you affected by CVE-2025-38499?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
