Loading vulnerability…
CVE-2025-38498 is an authorization flaw in the Linux kernel mount-handling function do_change_type(). The function allowed mount-propagation settings to be changed for unmounted mounts or mounts outside the caller's mount namespace. This violated mount-namespace isolation because propagation-setting operations were not subject to permission checks consistent with other mount(2) operations. The upstream fix rejects operations on unmounted mounts and mounts not located in the caller's mount namespace.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel mount-namespace permission-checking flaw in do_change_type(). The fix restricts changes to mount propagation settings to mounts located in the caller's mount namespace, aligning the checks with the rest of mount(2).
Referenced by the TuxCare CentOS 8.5 security advisory; no vulnerability details are provided.
A locally exploitable, low-complexity vulnerability requiring low privileges that can cause a high availability impact (denial of service); confidentiality and integrity impact are listed as none.
A Linux kernel vulnerability in do_change_type() involving operation on unmounted or unauthorized mounts.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.