CVE-2026-99296

published 16 Nov 2026 · updated 20 Nov 2026

libceph: bound mon_command ack decode to front len

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c6696ac94c8c3ad79a9fa57fc334af2dc1a1f72e, Kernel 04a04953b4828bfd8efd4ea3e7e9ad7dac5b083b, Kernel 62b41a16d8603d4d809fda212f15c3e9c783a82b and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6305a3b415157759bfe4b50a643fac22ea229f5c <c6696ac94c8c3ad79a9fa57fc334af2dc1a1f72e, >=6305a3b415157759bfe4b50a643fac22ea229f5c <04a04953b4828bfd8efd4ea3e7e9ad7dac5b083b, >=6305a3b415157759bfe4b50a643fac22ea229f5c <62b41a16d8603d4d809fda212f15c3e9c783a82b, >=6305a3b415157759bfe4b50a643fac22ea229f5c <be9fa57665efae4060d17ab21675c1c033d54a80, =4.9c6696ac94c8c3ad79a9fa57fc334af2dc1a1f72e, 04a04953b4828bfd8efd4ea3e7e9ad7dac5b083b, 62b41a16d8603d4d809fda212f15c3e9c783a82b, be9fa57665efae4060d17ab21675c1c033d54a80
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=4.9.0 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99296 severity on Zeptric[![CVE-2026-99296](https://zeptric.io/badge/cve/CVE-2026-99296.svg)](https://zeptric.io/cve/CVE-2026-99296)