CyberSecBulletin
CVE-2026-23411NVD status: Analyzed

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-23411 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions a92c5e5086a87d082696245a8607666da3d80554, 667df93769c02ff581c77d2d8f162147e719c557, 3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to a92c5e5086a87d082696245a8607666da3d80554 or 667df93769c02ff581c77d2d8f162147e719c557 or 3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc or ae10787d955fb255d381e0d5589451dd72c614b1, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.253 or 5.15.203 or 6.1.169 or 6.6.130, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxc961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, a92c5e5086a87d082696245a8607666da3d80554; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, 667df93769c02ff581c77d2d8f162147e719c557; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, 3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, ae10787d955fb255d381e0d5589451dd72c614b1; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, eecce026399917f6efa532c56bc7a3e9dd6ee68b; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, 13bc2772414d68e94e273dea013181a986948ddf; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, 2a732ed26fbd048e7925d227af8cf9ea43fb5cc9; c961ee5f21b202dea60b63eeef945730d92e46a6 up to, but not including, 8e135b8aee5a06c52a4347a5a6d51223c6f36ba3; and 1 more rangesa92c5e5086a87d082696245a8607666da3d80554, 667df93769c02ff581c77d2d8f162147e719c557, 3ddb961d2929bbb3204a2bba21b5d8153cd3f7cc, ae10787d955fb255d381e0d5589451dd72c614b1, eecce026399917f6efa532c56bc7a3e9dd6ee68b, 13bc2772414d68e94e273dea013181a986948ddf
LinuxLinux Kernel4.13.1 up to, but not including, 5.10.253; 5.11 up to, but not including, 5.15.203; 5.16 up to, but not including, 6.1.169; 6.2 up to, but not including, 6.6.130; 6.7 up to, but not including, 6.12.77; 6.13 up to, but not including, 6.18.18; 6.19 up to, but not including, 6.19.8; 4.13; and 1 more ranges5.10.253, 5.15.203, 6.1.169, 6.6.130, 6.12.77, 6.18.18

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Concurrent Execution using Shared Resource with Improper Synchronization

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How developers prevent this class of flaw

  • In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
  • Use thread-safe capabilities such as the data access abstraction in Spring.
  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

More Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities (CWE-362)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.