In the Linux kernel, the following vulnerability has been resolved: fuse-uring: make a fuse_req on SQE commit only findable after memcpy Bad… (CVE-2026-64259)
A use-after-free vulnerability in the Linux kernel's fuse-uring subsystem was resolved by changing the timing of when fuse requests become findable during SQE commit processing. Malicious userspace could previously send commit SQEs with request identifiers not yet sent to the fuse-server, potentially causing unsafe memory operations. The fix moves the fuse_uring_add_to_pq() call to after memcpy operations, preventing premature request visibility and race conditions.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel fuse-uring implementation involved a race condition where a fuse request could be found and manipulated before it was fully prepared and sent to the fuse-server. Specifically, fuse_uring_commit_fetch() could end a request with an incorrect state, leading to a use-after-free during memcpy in fuse_uring_send_in_task(). The patch changes the code to call fuse_uring_add_to_pq() only after the memcpy operations, ensuring the request is not findable by userspace until preparation is complete, thus preventing the race and use-after-free.
Potential Impact
This vulnerability could allow malicious userspace processes to trigger a use-after-free condition in the kernel, potentially leading to memory corruption or kernel crashes. However, no known exploits in the wild have been reported. The impact is limited to local userspace processes interacting with the fuse-uring interface.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by reordering operations in the fuse-uring code. Users should apply the official kernel updates that include this patch. Since this is a kernel-level fix, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the vendor or kernel mailing lists for the specific fixed versions.
In the Linux kernel, the following vulnerability has been resolved: fuse-uring: make a fuse_req on SQE commit only findable after memcpy Bad… (CVE-2026-64259)
Description
A use-after-free vulnerability in the Linux kernel's fuse-uring subsystem was resolved by changing the timing of when fuse requests become findable during SQE commit processing. Malicious userspace could previously send commit SQEs with request identifiers not yet sent to the fuse-server, potentially causing unsafe memory operations. The fix moves the fuse_uring_add_to_pq() call to after memcpy operations, preventing premature request visibility and race conditions.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel fuse-uring implementation involved a race condition where a fuse request could be found and manipulated before it was fully prepared and sent to the fuse-server. Specifically, fuse_uring_commit_fetch() could end a request with an incorrect state, leading to a use-after-free during memcpy in fuse_uring_send_in_task(). The patch changes the code to call fuse_uring_add_to_pq() only after the memcpy operations, ensuring the request is not findable by userspace until preparation is complete, thus preventing the race and use-after-free.
Potential Impact
This vulnerability could allow malicious userspace processes to trigger a use-after-free condition in the kernel, potentially leading to memory corruption or kernel crashes. However, no known exploits in the wild have been reported. The impact is limited to local userspace processes interacting with the fuse-uring interface.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by reordering operations in the fuse-uring code. Users should apply the official kernel updates that include this patch. Since this is a kernel-level fix, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the vendor or kernel mailing lists for the specific fixed versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6vp8-rvj5-gc8c
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64259"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420f9c2644c7f8086c4f
Added to database: 07/25/2026, 23:09:03 UTC
Last enriched: 07/25/2026, 23:43:43 UTC
Last updated: 07/26/2026, 05:06:18 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.