Race condition in Linux kernel AppArmor i_private handling
CVE-2026-23411 is a Linux kernel AppArmor vulnerability caused by a race between releasing data referenced from an inode's i_private field and subsequent filesystem callbacks that may still access that data. AppArmor removed the original filesystem entry and then dropped its reference to the associated i_private data, but the inode could remain alive beyond that point. As a result, later fs callback functions could dereference data that had already been freed, creating a use-after-free style condition. The issue is most likely to affect rawdata and loaddata objects because they have the fewest references, though other AppArmor data types stored in i_private may also be reachable with carefully crafted triggering conditions. The fix moves the put/release of i_private-referenced data to inode eviction, where the lifetime is correctly synchronized with inode teardown.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.