CVE-2026-68433: Linux kernel · libceph: bound get_version reply decode to front len
Affects Linux kernelSource CVE Database V5
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
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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
- git.kernel.org/stable/c/1307028f082756bf453e1889aee9983d30643a4b (opens in a new tab)
- git.kernel.org/stable/c/f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e (opens in a new tab)
- git.kernel.org/stable/c/72a35070fcefa229b1b031aa7482ad3788e18f07 (opens in a new tab)
- git.kernel.org/stable/c/340e0386aa39da181015bee38f309018c335ce16 (opens in a new tab)
- git.kernel.org/stable/c/d60de8253c85a02d0e6194b0735e7a562981a04c (opens in a new tab)
- git.kernel.org/stable/c/4e7ebfaa0d14cf50e44041bfde38070d6dbc019f (opens in a new tab)
- git.kernel.org/stable/c/0d934c934ec746d53fc7e4f53239792647bbae63 (opens in a new tab)
- git.kernel.org/stable/c/d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 (opens in a new tab)