CVE-2026-99293
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:
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.
Technical details traces, logs and code from the original report
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)
Timeline
Built from our own data: NVD, CISA KEV and other exploitation catalogues, FIRST EPSS, public exploits, specialised media and Orbitaley coverage.
- CVE record published in NVD
Affected technologies (1)
⚠ AI-inferred from the description — NVD hasn't analyzed this CVE yet, these aren't verified CPEs.
NVD record
- NVD status
- Received
- Published
- Nov 16, 2026
- Last modified
- Nov 16, 2026
- CVSS
- NVD hasn't assigned a CVSS score to this CVE (common since the April 2026 policy change).
References
Raw JSON (NVD)
Show
{
"id": "CVE-2026-99293",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "c090c8abae4b6b77a1bee116aa6c385456ebef96",
"lessThan": "61adcab593ff6bb806ba09df8c2c3d7e19edc908",
"versionType": "git"
},
{
"status": "affected",
"version": "c090c8abae4b6b77a1bee116aa6c385456ebef96",
"lessThan": "10a58bf0107a02854584ed79281d05a84d62d900",
"versionType": "git"
},
{
"status": "affected",
"version": "c090c8abae4b6b77a1bee116aa6c385456ebef96",
"lessThan": "c1338aae7b4054e26f322155423f6aba90aeea23",
"versionType": "git"
}
],
"programFiles": [
"fs/fuse/dev.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.14"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.14",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver",
"lessThanOrEqual": "7.3.*"
},
{
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"fs/fuse/dev.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-11-16T10:17:01.900",
"references": [
{
"url": "https://git.kernel.org/stable/c/10a58bf0107a02854584ed79281d05a84d62d900",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/61adcab593ff6bb806ba09df8c2c3d7e19edc908",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c1338aae7b4054e26f322155423f6aba90aeea23",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: don't BUG when the copy buffer is exhausted\n\nfuse_copy_fill() hits BUG_ON(!err) once the iterator backing the copy\nruns out of pages. Over io-uring the amount copied is not bounded by the\npayload buffer the server registered, so an unprivileged user can drain\nthe iterator and panic the host - mount a FUSE filesystem with small\npayload buffers, then setxattr() a larger value:\n\n kernel BUG at fs/fuse/dev.c:1064!\n Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n CPU: 1 UID: 0 PID: 148 Comm: exploit Not tainted 7.3.0-rc1 #2\n RIP: 0010:fuse_copy_fill (fs/fuse/dev.c:1033)\n Call Trace:\n <TASK>\n fuse_copy_args (fs/fuse/dev.c:1354 fs/fuse/dev.c:1380)\n fuse_uring_args_to_ring (fs/fuse/dev_uring.c:891)\n fuse_uring_prepare_send (fs/fuse/dev_uring.c:940 fs/fuse/dev_uring.c:1057)\n fuse_uring_send_in_task (fs/fuse/dev_uring.c:1745)\n tctx_task_work_run (io_uring/tw.c:96)\n tctx_task_work (io_uring/tw.c:133)\n task_work_run (kernel/task_work.c:233)\n io_run_task_work (io_uring/tw.h:84)\n io_cqring_wait (io_uring/wait.c:278)\n __do_sys_io_uring_enter (io_uring/io_uring.c:2676)\n do_syscall_64 (arch/x86/entry/syscall_64.c:61)\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)\n\nThe reply path can drain it the same way, via the server-supplied\npayload_sz in fuse_uring_copy_from_ring().\n\nReturn -EIO instead. All three fuse_copy_fill() callers already\npropagate the error."
}
],
"lastModified": "2026-11-16T10:17:01.900",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}