CVE-2026-64260

Analyzed Analyzed - Analysis Complete

Race Condition in Linux Kernel FUSE-URING Subsystem

Publication date: 2026-07-25

Last updated on: 2026-08-12

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-25

Last Modified

2026-08-12

Generated

2026-08-14

AI Q&A

2026-07-25

EPSS Evaluated

2026-08-13

NVD

CVE-2026-64260

EUVD

EUVD-2026-48972

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.19 (inc) to 7.1.4 (exc)
linux	linux_kernel	From 6.14 (inc) to 6.18.39 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	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.

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves race conditions in the fuse-uring subsystem. Specifically, it affects how the queue->stopped flag is accessed and modified. Some parts of the code check this flag under a lock, but fuse_uring_commit_fetch() does not, and fuse_uring_abort_end_requests() does not set the flag under a lock. This can lead to issues where a 'struct fuse_req' might be freed while another thread is still performing teardown work.

Detection Guidance

This vulnerability is specific to the Linux kernel's fuse-uring component and involves race conditions in queue handling. Detection requires checking kernel logs for fuse-related errors or crashes, particularly during high I/O load. Commands like dmesg | grep fuse or journalctl -k | grep fuse may help identify issues. Kernel version checks (uname -r) can confirm if your system is affected.

Impact Analysis

This vulnerability could lead to system instability or crashes due to race conditions in the kernel's fuse-uring subsystem. It may cause unexpected behavior, data corruption, or denial of service if exploited by an attacker with local access.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it pertains to a race condition in the Linux kernel's fuse-uring subsystem. Compliance impacts would depend on how the affected system is used in a broader context, not the vulnerability itself.

Mitigation Strategies

Update the Linux kernel to the latest stable version that includes the fix for CVE-2026-64260. If immediate patching is not possible, consider disabling fuse-uring functionality temporarily or restricting its use to trusted applications until the update is applied.

Hi! I’m here to help you understand CVE-2026-64260. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70