CyberSecBulletin
CVE-2026-64010NVD status: Analyzed

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-64010 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions dce85215a6c7b0fd753f577a4c487f647119884c, bd08bb7443c501d2f2a71d529e4afcf11c9b07d2, 0b45c31746e1523d5d482fda8fcf54a35ac417f1 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.2% 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 dce85215a6c7b0fd753f577a4c487f647119884c or bd08bb7443c501d2f2a71d529e4afcf11c9b07d2 or 0b45c31746e1523d5d482fda8fcf54a35ac417f1 or ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.259 or 5.15.210 or 6.1.176 or 6.6.143, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxa69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, dce85215a6c7b0fd753f577a4c487f647119884c; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, bd08bb7443c501d2f2a71d529e4afcf11c9b07d2; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, 0b45c31746e1523d5d482fda8fcf54a35ac417f1; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, ad8a27d63cac96bac441edd002209ebd996e12fb; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, 650bdd8fdfab64a09ee474150313dbc48c374795; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183; a69f32af86e389dd232b1bb2269e202c1bfcc60f up to, but not including, b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77; and 1 more rangesdce85215a6c7b0fd753f577a4c487f647119884c, bd08bb7443c501d2f2a71d529e4afcf11c9b07d2, 0b45c31746e1523d5d482fda8fcf54a35ac417f1, ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2, ad8a27d63cac96bac441edd002209ebd996e12fb, 650bdd8fdfab64a09ee474150313dbc48c374795
LinuxLinux Kernel3.6 up to, but not including, 5.10.259; 5.11 up to, but not including, 5.15.210; 5.16 up to, but not including, 6.1.176; 6.2 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.93; 6.13 up to, but not including, 6.18.35; 6.19 up to, but not including, 7.0.12; 7.15.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.35

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
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() A race condition exists in the NFC LLCP connection state machine where the connection acceptance packet (CC) can be processed concurrently with socket release. This can lead to a use-after-free of the socket object. When nfc_llcp_recv_cc() moves the socket from the connecting_sockets list to the sockets list, it does so without holding the socket lock. If llcp_sock_release() is executing concurrently, it might have already unlinked the socket and dropped its references, which can result in nfc_llcp_recv_cc() linking a freed socket into the live list. Fix this by holding lock_sock() during the state transition and list movement in nfc_llcp_recv_cc(). After acquiring the lock, check if the socket is still hashed to ensure it hasn't already been unlinked and marked for destruction by the release path. This aligns the locking pattern with recv_hdlc() and recv_disc().

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.