Skip to main content
VulnerabilityPublished Updated

CVE-2026-68433: Linux kernel · libceph: bound get_version reply decode to front len

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High · fixed in f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e, d60de8253c85a02d0e6194b0735e7a562981a04c, d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e
Fixed in
  • f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e
LinuxLinuxAffected
  • ≥ 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < d60de8253c85a02d0e6194b0735e7a562981a04c
Fixed in
  • d60de8253c85a02d0e6194b0735e7a562981a04c
LinuxLinuxAffected
  • ≥ 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0
Fixed in
  • d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0
LinuxLinuxAffected
  • ≥ 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 1307028f082756bf453e1889aee9983d30643a4b
Fixed in
  • 1307028f082756bf453e1889aee9983d30643a4b
LinuxLinuxAffected
  • ≥ 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 340e0386aa39da181015bee38f309018c335ce16
Fixed in
  • 340e0386aa39da181015bee38f309018c335ce16
LinuxLinuxAffected
  • ≥ 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 72a35070fcefa229b1b031aa7482ad3788e18f07
Fixed in
  • 72a35070fcefa229b1b031aa7482ad3788e18f07

Description

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.

References

Community reviews

Loading reviews…