CVE-2024-46695 is an incorrect authorization vulnerability in the Linux kernel SELinux and Smack inode_setsecctx hook. When processing NFS security-context updates, the affected path used __vfs_setxattr_noperm(), which assumes that all required authorization checks have already been made. Although nfsd_setattr() performed file-handle and NFS permission validation, those checks did not fully enforce the checks performed by security_inode_setxattr() and associated LSM hooks. Consequently, root on an NFS client could alter security labels of files on an NFS export despite root squashing being enabled.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel SELinux/Smack permission-check bypass in the inode_setsecctx hook.
Linux kernel SELinux and SMACK flaw that could bypass a permissions check in the inode_setsecctx hook.
Linux kernel SELinux/Smack permissions-check bypass in the inode_setsecctx hook.
A Linux kernel SELinux/SMACK permissions-check bypass in the inode_setsecctx hook.
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.