CVE-2025-38499
clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns
Reported by linux · Published August 11, 2025
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel-headers | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel-libbpf-static | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel-devel | Amazon Linux | 4.14.355-280.684.amzn2 |
| kernel6.12-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel-tools-devel | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel6.12-libbpf-static | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| linux_kernel | linux | 6.15.3, 6.12.40, 6.6.100, 6.1.147, 5.15.190, 5.14, 5.11, 5.5, 4.20, 4.15, 4.10, 4.5 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 427215d85e8d1476da1a86b8d67aceb485eb3631, 427215d85e8d1476da1a86b8d67aceb485eb3631, 427215d85e8d1476da1a86b8d67aceb485eb3631 |
| Linux | Linux | 5.14, 0, 5.15.190 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2 | kernel-devel | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | 3.1.5 |
| linux | linux_kernel | 4.9.280, 5.13.11, 5.10.59 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2 | kernel | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | 3.1.5 |
| amazon:2 | python-perf | 0 |
…and 24 more
Timeline
- Aug 8, 2025 CVE Published
- Aug 12, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (16 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (148 in total, the first dated here)
- Mar 29, 2026 Security Advisory (177 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38499
vulnetix vdb fixes CVE-2025-38499
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38499/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart