CVE-2026-64259CWE-416

CVE-2026-64259

High · published July 25, 2026

CVSS v3.1
7.8
EPSS
0%
Percentile
5.0
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.8 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00161 · 5.0th percentile
Weakness
CWE-416 · Use After Free
Published
2026-07-25T14:17Z
Affected products (2)
ProductVersionsFixed in
linux/linux_kernel≥ 6.14, < 6.18.396.18.39
linux/linux_kernel≥ 6.19, < 7.1.47.1.4
References (3)
EPSS history
Timeline
  • 25 JUL 08:49Z
    fuse-uring: make a fuse_req on SQE commit only findable after memcpy
    cvelistv5