Loading vulnerability…
CVE-2025-38396 is an access-control bypass in Linux kernel secretmem anonymous-inode handling. Following allocation of a secretmem anonymous inode, the S_PRIVATE flag was not cleared. As a result, LSM hooks, including SELinux checks, could be bypassed for secretmem file descriptors. The corrective change uses secure anonymous-inode creation through anon_inode_make_secure_inode() and exports that helper for use by KVM guest_memfd, replacing manual security-context initialization.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel secretmem Linux Security Module bypass vulnerability.
A Linux kernel filesystem/security fix addressing a secretmem LSM bypass involving anon_inode_make_secure_inode().
A Linux kernel secretmem security regression that could bypass LSM/SELinux checks on secretmem file descriptors because the S_PRIVATE flag remained set after anonymous inode allocation. The fix also provides guest_memfd/KVM with a supported way to create anonymous inodes carrying the proper security context.
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.