CyberSecBulletin
CVE-2026-23410NVD status: Analyzed

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

CVE-2026-23410 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 3b8e77c7abab40e6de9ad9de730d77984a498840, d9d8560b9b7932f8cffc4c068c14289220900f79, 6b6ba87579c7e7c669e0bec91823e7fb693bc5df 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.14% 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 3b8e77c7abab40e6de9ad9de730d77984a498840 or d9d8560b9b7932f8cffc4c068c14289220900f79 or 6b6ba87579c7e7c669e0bec91823e7fb693bc5df or 6ef1f2926c41ab96952d9696d55a052f1b3a9418, 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
LinuxLinux5d5182cae40115c03933989473288e54afb39c7c up to, but not including, 3b8e77c7abab40e6de9ad9de730d77984a498840; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, d9d8560b9b7932f8cffc4c068c14289220900f79; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, 6b6ba87579c7e7c669e0bec91823e7fb693bc5df; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, 6ef1f2926c41ab96952d9696d55a052f1b3a9418; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, f9761add6d100962a23996cb68f3d6abdd4d1815; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, af782cc8871e3683ddd5a3cd2f7df526599863a9; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, 763e838adc3c7ec5a7df2990ce84cad951e42721; 5d5182cae40115c03933989473288e54afb39c7c up to, but not including, a0b7091c4de45a7325c8780e6934a894f92ac86b; and 1 more ranges3b8e77c7abab40e6de9ad9de730d77984a498840, d9d8560b9b7932f8cffc4c068c14289220900f79, 6b6ba87579c7e7c669e0bec91823e7fb693bc5df, 6ef1f2926c41ab96952d9696d55a052f1b3a9418, f9761add6d100962a23996cb68f3d6abdd4d1815, af782cc8871e3683ddd5a3cd2f7df526599863a9
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 on rawdata dereference There is a race condition that leads to a use-after-free situation: because the rawdata inodes are not refcounted, an attacker can start open()ing one of the rawdata files, and at the same time remove the last reference to this rawdata (by removing the corresponding profile, for example), which frees its struct aa_loaddata; as a result, when seq_rawdata_open() is reached, i_private is a dangling pointer and freed memory is accessed. The rawdata inodes weren't refcounted to avoid a circular refcount and were supposed to be held by the profile rawdata reference. However during profile removal there is a window where the vfs and profile destruction race, resulting in the use after free. Fix this by moving to a double refcount scheme. Where the profile refcount on rawdata is used to break the circular dependency. Allowing for freeing of the rawdata once all inode references to the rawdata are put.

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.