CVE-2026-99296 libceph: bound mon_command ack decode to front len
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:
libceph: bound mon_command ack decode to front len
handle_command_ack() bounds the decode with msg->front_alloc_len, the size
of the reply buffer, instead of msg->front.iov_len, the number of bytes the
monitor sent. mon_alloc_msg() routes every CEPH_MSG_MON_COMMAND_ACK to
get_generic_reply(), which returns the preallocated ->reply of whichever
generic request carries the same tid, so the buffer keeps its fixed size
however short the reply is. An ack with hdr.front_len below sizeof(struct
ceph_mon_request_header) + sizeof(u32), including 0, still passes
ceph_decode_need(), and ceph_decode_32() returns four bytes that were never
received: uninitialized slab memory, stale bytes of an earlier message, or
bytes the peer planted by sending a reply that lands in the same buffer and
is then rejected. The read stays within the allocation, so KASAN does not
flag it.
req->result reaches userspace through ceph_monc_do_statfs(),
ceph_monc_get_version() and ceph_monc_blocklist_add(); rbd hands it back
from write() on /sys/bus/rbd/add_single_major, and rbd_get_client() passes
it to ERR_PTR() unchecked, which faults:
rbd: failed to get latest osdmap: -186318427
BUG: unable to handle page fault for address: fffffbfffe9ca034
Oops: Oops: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:do_rbd_add (drivers/block/rbd.c:7105)
Call Trace:
...
kernfs_fop_write_iter (fs/kernfs/file.c:345)
vfs_write (fs/read_write.c:595 fs/read_write.c:687)
ksys_write (fs/read_write.c:739)
do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)
Kernel panic - not syncing: Fatal exception
Use msg->front.iov_len, matching handle_subscribe_ack(),
handle_statfs_reply(), handle_get_version_reply() and handle_auth_reply().
A well-formed ack has front.iov_len >= 22 and is unaffected; a short one
takes the existing bad: path. This applies commit d3c32939fa0e ("libceph:
bound get_version reply decode to front len") to the last decode-side
use of front_alloc_len in this file.
- 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.12.117
- Linux Linux: fixed in 6.18.61
- Linux Linux: fixed in 7.3.2
- Linux Linux: fixed in 7.4-rc1
- Debian: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-99296 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99296?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99296?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-99296 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 | 4.9 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.117 |
| 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 | 12, 14 | linux | no fix listed | DEBIAN-CVE-2026-99296 |
| Debian | 13 | linux | 6.12.117-1 | DEBIAN-CVE-2026-99296 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | Pro:14.04:LTS | linux, linux-aws, linux-azure and 1 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | Pro:16.04:LTS | linux, linux-aws, linux-gcp and 5 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | Pro:18.04:LTS | linux, linux-aws, linux-kvm and 10 more | no fix listed | UBUNTU-CVE-2026-99296 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2026-99296 |
| 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.