CVE-2026-23411apparmor: fix race between freeing data and fs accessing it
- 7.8HighCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix race between freeing data and fs accessing it AppArmor was putting the reference to i_private data on its end after removing the original entry from the file system. However the inode can aand does live beyond that point and it is possible that some of the fs call back functions will be invoked after the reference has been put, which results in a race between freeing the data and accessing it through the fs. While the rawdata/loaddata is the most likely candidate to fail the race, as it has the fewest references. If properly crafted it might be possible to trigger a race for the other types stored in i_private. Fix this by moving the put of i_private referenced data to the correct place which is during inode eviction.
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < a92c5e5086a87d082696245a8607666da3d80554
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < 667df93769c02ff581c77d2d8f162147e719c557
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < 3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < ae10787d955fb255d381e0d5589451dd72c614b1
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < eecce026399917f6efa532c56bc7a3e9dd6ee68b
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < 13bc2772414d68e94e273dea013181a986948ddf
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < 2a732ed26fbd048e7925d227af8cf9ea43fb5cc9
- affected c961ee5f21b202dea60b63eeef945730d92e46a6 – < 8e135b8aee5a06c52a4347a5a6d51223c6f36ba3
- affected 4.13
- unaffected < 4.13
- unaffected 5.10.253 – ≤ 5.10.*
- unaffected 5.15.203 – ≤ 5.15.*
- unaffected 6.1.169 – ≤ 6.1.*
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.77 – ≤ 6.12.*
- unaffected 6.18.18 – ≤ 6.18.*
- unaffected 6.19.8 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References8
- https://git.kernel.org/stable/c/a92c5e5086a87d082696245a8607666da3d80554 (opens in a new tab)
- https://git.kernel.org/stable/c/667df93769c02ff581c77d2d8f162147e719c557 (opens in a new tab)
- https://git.kernel.org/stable/c/3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc (opens in a new tab)
- https://git.kernel.org/stable/c/ae10787d955fb255d381e0d5589451dd72c614b1 (opens in a new tab)
- https://git.kernel.org/stable/c/eecce026399917f6efa532c56bc7a3e9dd6ee68b (opens in a new tab)
- https://git.kernel.org/stable/c/13bc2772414d68e94e273dea013181a986948ddf (opens in a new tab)
- https://git.kernel.org/stable/c/2a732ed26fbd048e7925d227af8cf9ea43fb5cc9 (opens in a new tab)
- https://git.kernel.org/stable/c/8e135b8aee5a06c52a4347a5a6d51223c6f36ba3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-17843 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23411)Record last updated .