DEBIAN-CVE-2025-38499
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.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Debian:14 | linux | 0, 6.12.38-1, 6.12.41-1 |
| Debian:11 | linux | 6.11, 6.19.13-1, 6.19.14-1 |
| Debian:11 | linux-6.1 | 6.1.128-1, 6.1.119-1, 6.1.112-1 |
| Debian:12 | linux | 6.1.67-1, 6.1.69-1, 6.1.69-1~bpo11+1 |
| Debian:13 | linux | 6.12.38-1, 0, 6.12.38-1 |
Timeline
- Aug 11, 2025 CVE Published
- Apr 28, 2026 CVE Updated