CVE-2026-64259

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.

Package Linux Kernel
Published 2026-07-25
Last modified 2026-07-25
Patch available
Yes

Affected versions

Linux kernel versions 6.14 and later are affected. Fixed in 6.18.39, 7.1.4, 7.2-rc1 and their respective stable series.

Affected from
≥ 6.14
Fixed in
✓ 6.18.39 6.18.x ✓ 7.1.4 7.1.x ✓ 7.2-rc1

Frequently asked questions

  • What is CVE-2026-64259?

    CVE-2026-64259 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.14 onward and has been patched in 6.18.39, 7.1.4 and 7.2-rc1. CVE-2026-64259 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64259?

    Yes. CVE-2026-64259 has been patched. Fixed versions include 6.18.39, 7.1.4 and 7.2-rc1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64259 actively exploited?

    No. CVE-2026-64259 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.