CVE-2026-99293 fuse: don't BUG when the copy buffer is exhausted
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
In the Linux kernel, the following vulnerability has been resolved:
fuse: don't BUG when the copy buffer is exhausted
fuse_copy_fill() hits BUG_ON(!err) once the iterator backing the copy
runs out of pages. Over io-uring the amount copied is not bounded by the
payload buffer the server registered, so an unprivileged user can drain
the iterator and panic the host - mount a FUSE filesystem with small
payload buffers, then setxattr() a larger value:
kernel BUG at fs/fuse/dev.c:1064!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 1 UID: 0 PID: 148 Comm: exploit Not tainted 7.3.0-rc1 #2
RIP: 0010:fuse_copy_fill (fs/fuse/dev.c:1033)
Call Trace:
<TASK>
fuse_copy_args (fs/fuse/dev.c:1354 fs/fuse/dev.c:1380)
fuse_uring_args_to_ring (fs/fuse/dev_uring.c:891)
fuse_uring_prepare_send (fs/fuse/dev_uring.c:940 fs/fuse/dev_uring.c:1057)
fuse_uring_send_in_task (fs/fuse/dev_uring.c:1745)
tctx_task_work_run (io_uring/tw.c:96)
tctx_task_work (io_uring/tw.c:133)
task_work_run (kernel/task_work.c:233)
io_run_task_work (io_uring/tw.h:84)
io_cqring_wait (io_uring/wait.c:278)
__do_sys_io_uring_enter (io_uring/io_uring.c:2676)
do_syscall_64 (arch/x86/entry/syscall_64.c:61)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
The reply path can drain it the same way, via the server-supplied
payload_sz in fuse_uring_copy_from_ring().
Return -EIO instead. All three fuse_copy_fill() callers already
propagate the error.
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
- Published
- Assigned by
- Linux (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.18.61
- Linux Linux: fixed in 7.3.2
- Linux Linux: fixed in 7.4-rc1
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-99293 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99293?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99293?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99293 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.14 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.18 | 6.18.61 |
| Linux | 7.3 | 7.3.2 |
| Linux | later releases | 7.4-rc1 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | no fix listed | DEBIAN-CVE-2026-99293 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | Pro:14.04:LTS | linux, linux-aws, linux-azure and 1 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | Pro:16.04:LTS | linux, linux-aws, linux-gcp and 5 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | Pro:18.04:LTS | linux, linux-aws, linux-kvm and 10 more | no fix listed | UBUNTU-CVE-2026-99293 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2026-99293 |
| 4 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.