CVE-2026-64259
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.
Affected products
6- osv-coords4 versionspkg:apk/chainguard/linux-gcp-6.18pkg:apk/chainguard/linux-gcp-6.18-bootcpkg:linux/kernelpkg:rpm/opensuse/kernel-source&distro=openSUSE%20Tumbleweed
< 6.18.44-r0+ 3 more
- (no CPE)range: < 6.18.44-r0
- (no CPE)range: < 6.18.44-r0
- (no CPE)range: >= 6.14.0, < 6.18.39
- (no CPE)range: < 7.1.7-1.1
Patches
Vulnerability mechanics
References
3News mentions
0No linked articles in our index yet.