CVE-2026-68433High· 8.6▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: libceph: bound get_version reply decode to front len handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is th…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 47.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
Last analysed / modified upstream
0.3% → 0.4%
In the Linux kernel, the following vulnerability has been resolved:
libceph: bound get_version reply decode to front len
handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually received.
A truncated reply can therefore pass ceph_decode_need() and decode the second u64 from stale tail bytes left in the buffer by an earlier message, causing an uninitialized memory read.
Use msg->front.iov_len as the receive-side decode boundary, matching other libceph reply handlers and limiting decoding to the bytes that were actually read from the wire.
Linux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < 1307028f082756bf453e1889aee9983d30643a4bLinux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2eLinux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < 72a35070fcefa229b1b031aa7482ad3788e18f07Linux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < 340e0386aa39da181015bee38f309018c335ce16Linux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < d60de8253c85a02d0e6194b0735e7a562981a04cLinux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < 4e7ebfaa0d14cf50e44041bfde38070d6dbc019fLinux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < 0d934c934ec746d53fc7e4f53239792647bbae63Linux >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 < d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0Linux 3.16Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets