CVE-2026-64259
Last modified
CVE-2026-64259 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: fuse-uring: make a fuse_req on SQE commit only findable after memcpy Bad userspace might try to trick us and send commit SQEs request unique / commit-id of requests that are not even send to fuse-server (io_uring_cmd_done() not called) yet. fuse_uring_commit_fetch() ends the fuse request when the ring entry has a wrong state, but that could have caused a use-after-free with the memcpy operations in fuse_uring_send_in_task(). In order to avoid such races the call of fuse_uring_add_to_pq() is moved after the copy operations and just before completing the io-uring request - malicious userspace cannot find the request anymore until all prepration work in fuse-client/kernel is completed. This also moves fuse_uring_add_to_pq() a bit up in the code to avoid a forward declaration. Also not with a preparation commit, to make it easier to back port to older kernels.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: fuse-uring: make a fuse_req on SQE commit only findable after memcpy Bad userspace might try to trick us and send commit SQEs request unique / commit-id of requests that are not even send to fuse-server (io_uring_cmd_done() not called) yet. fuse_uring_commit_fetch() ends the fuse request when the ring entry has a wrong state, but that could have caused a use-after-free with the memcpy operations in fuse_uring_send_in_task(). In order to avoid such races the call of fuse_uring_add_to_pq() is moved after the copy operations and just before completing the io-uring request - malicious userspace cannot find the request anymore until all prepration work in fuse-client/kernel is completed. This also moves fuse_uring_add_to_pq() a bit up in the code to avoid a forward declaration. Also not with a preparation commit, to make it easier to back port to older kernels.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.14, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64259?
How severe is CVE-2026-64259?
How do I fix CVE-2026-64259?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64253In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64254In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64255In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64256In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64257In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-64258In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6426A type mismatch vulnerability was found in QEMU's vhost infl…4.4
- CVE-2026-64260In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64261In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64262In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64263In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64264In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64259?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
