CVE-2026-99296
libceph: bound mon_command ack decode to front len
No exploitation reported by the sources we read.
- Published2026-11-16
- Fixed in7.3.2 · 6.18.61 · 6.12.117
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-11-1609:59CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.2 | 7.3.2 | OSV |
| 6.x | ≥ 6.13.0, < 6.18.61 | 6.18.61 | OSV |
| 6.12 | ≥ 4.9.0, < 6.12.117 | 6.12.117 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 6305a3b415157759bfe4b50a643fac22ea229f5c, < c6696ac94c8c3ad79a9fa57fc334af2dc1a1f72efixed in c6696ac94c8c3ad79a9fa57fc334af2dc1a1f72egit
- ≥ 6305a3b415157759bfe4b50a643fac22ea229f5c, < 04a04953b4828bfd8efd4ea3e7e9ad7dac5b083bfixed in 04a04953b4828bfd8efd4ea3e7e9ad7dac5b083bgit
- ≥ 6305a3b415157759bfe4b50a643fac22ea229f5c, < be9fa57665efae4060d17ab21675c1c033d54a80fixed in be9fa57665efae4060d17ab21675c1c033d54a80git
- ≥ 6305a3b415157759bfe4b50a643fac22ea229f5c, < 62b41a16d8603d4d809fda212f15c3e9c783a82bfixed in 62b41a16d8603d4d809fda212f15c3e9c783a82bgit
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 4.9no fix stated
Not affected < 4.9 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAzure Linux:3all versions · no fixed version listed
- linuxUbuntu:Pro:20.04:LTSall versions · no fixed version listedand 21 other packages
- linuxUbuntu:Pro:18.04:LTSall versions · no fixed version listedand 12 other packages
- linuxUbuntu:26.10all versions · no fixed version listedand 8 other packages
- linuxUbuntu:26.04:LTSall versions · no fixed version listedand 14 other packages
- linuxUbuntu:24.04:LTSall versions · no fixed version listedand 52 other packages
- linuxUbuntu:22.04:LTSall versions · no fixed version listedand 59 other packages
- linuxDebian:14all versions · fixed in 7.3.3-1
21 more package ranges on OSV.dev
Fix
- Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-19
- CNACVSS 3.17.12026-11-19
- FIRST EPSSEPSS score0.2 %2026-11-18
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-114239same flawAzure Linux · MIT
- EUVD-2026-126202same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-p2cm-fx34-7984same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
- Published
- 2026-11-16
- Last Modified
- 2026-11-19
- NVD status
- Received
- GitHub Advisory
- GHSA-p2cm-fx34-7984
Frequently asked questions
What is CVE-2026-99296?
Is CVE-2026-99296 actively exploited?
What is the CVSS score for CVE-2026-99296?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-p2cm-fx34-7984
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served