CVE-2026-23411
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.169
- Linux Kernel < 6.6.130
- Linux Kernel < 6.12.77
- Linux Kernel < 6.18.18
- Linux Kernel < 6.19.8
- Linux Kernel 4.13
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23411.md and follow it. Check whether this project is affected by CVE-2026-23411. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/13bc2772414d68e94e273dea013181a986948ddf
- https://git.kernel.org/stable/c/2a732ed26fbd048e7925d227af8cf9ea43fb5cc9
- https://git.kernel.org/stable/c/3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc
- https://git.kernel.org/stable/c/667df93769c02ff581c77d2d8f162147e719c557
- https://git.kernel.org/stable/c/8e135b8aee5a06c52a4347a5a6d51223c6f36ba3
- https://git.kernel.org/stable/c/a92c5e5086a87d082696245a8607666da3d80554
- https://git.kernel.org/stable/c/ae10787d955fb255d381e0d5589451dd72c614b1
- https://git.kernel.org/stable/c/eecce026399917f6efa532c56bc7a3e9dd6ee68b
References
- https://git.kernel.org/stable/c/13bc2772414d68e94e273dea013181a986948ddf
- https://git.kernel.org/stable/c/2a732ed26fbd048e7925d227af8cf9ea43fb5cc9
- https://git.kernel.org/stable/c/3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc
- https://git.kernel.org/stable/c/667df93769c02ff581c77d2d8f162147e719c557
- https://git.kernel.org/stable/c/8e135b8aee5a06c52a4347a5a6d51223c6f36ba3
- https://git.kernel.org/stable/c/a92c5e5086a87d082696245a8607666da3d80554
- https://git.kernel.org/stable/c/ae10787d955fb255d381e0d5589451dd72c614b1
- https://git.kernel.org/stable/c/eecce026399917f6efa532c56bc7a3e9dd6ee68b