CyberSecBulletin
CVE-2026-64260NVD status: Analyzed

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

CVE-2026-64260 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 39c8e925b207afceffaa5382416ed405e0223a03, 4021a3a79eee551d95fe1e1e7c1b195d34ba8c08, b70a3aca16934c196f92abb17b01c1647b9bb63c 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.13% 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 39c8e925b207afceffaa5382416ed405e0223a03 or 4021a3a79eee551d95fe1e1e7c1b195d34ba8c08 or b70a3aca16934c196f92abb17b01c1647b9bb63c, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.18.39 or 7.1.4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4a9bfb9b6850fec0685447aed280533cf980de70 up to, but not including, 39c8e925b207afceffaa5382416ed405e0223a03; 4a9bfb9b6850fec0685447aed280533cf980de70 up to, but not including, 4021a3a79eee551d95fe1e1e7c1b195d34ba8c08; 4a9bfb9b6850fec0685447aed280533cf980de70 up to, but not including, b70a3aca16934c196f92abb17b01c1647b9bb63c; 6.1439c8e925b207afceffaa5382416ed405e0223a03, 4021a3a79eee551d95fe1e1e7c1b195d34ba8c08, b70a3aca16934c196f92abb17b01c1647b9bb63c
LinuxLinux Kernel6.14 up to, but not including, 6.18.39; 6.19 up to, but not including, 7.1.46.18.39, 7.1.4

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

Official description

In the Linux kernel, the following vulnerability has been resolved: fuse-uring: Avoid queue->stopped races and set/read that value under lock There are several readers of queue->stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races 'struct fuse_req' might be freed with fuse_request_end, but another thread/cpu might already do teardown work.

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.