Go to homepageCyberStrike

Menu

Star on GitHub · 3.3k
Sign inDownload

CVE-2025-38499

7.8 · HIGH

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…

Published Aug 11, 2025EPSS 0.16%

Overview

CVE-2025-38499 is a high-severity vulnerability. It was published on August 11, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/36fecd740de2d542d2091d65d36554ee2bcf9c65Refgit.kernel.org/stable/c/38628ae06e2a37770cd794802a3f1310cf9846e3Refgit.kernel.org/stable/c/c28f922c9dcee0e4876a2c095939d77fe7e15116Refgit.kernel.org/stable/c/d717325b5ecf2a40daca85c61923e17f32306179Refgit.kernel.org/stable/c/dc6a664089f10eab0fb36b6e4f705022210191d2Refgit.kernel.org/stable/c/e77078e52fbf018ab986efb3c79065ab35025607Reflists.debian.org/debian-lts-announce/2025/10/msg00008.htmlRefcert-portal.siemens.com/productcert/html/ssa-082556.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-38499?

CVE-2025-38499 is a high-severity vulnerability. It was published on August 11, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-38499?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38499?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38499?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38499 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999