CVE-2026-68433libceph: bound get_version reply decode to front len
- 8.6HighCVSS base score
- 0.36%Exploitation in 30 daysEPSS · top 69% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 13 days later
· 13 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H |
| NVDNVD · Received | 3.1 | High8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H |
- EPSS (exploitation in 30 days)
- 0.36% · top 69% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.6.
Affected products
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < 1307028f082756bf453e1889aee9983d30643a4b
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < 72a35070fcefa229b1b031aa7482ad3788e18f07
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < 340e0386aa39da181015bee38f309018c335ce16
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < d60de8253c85a02d0e6194b0735e7a562981a04c
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < 4e7ebfaa0d14cf50e44041bfde38070d6dbc019f
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < 0d934c934ec746d53fc7e4f53239792647bbae63
- affected 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 – < d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0
- affected 3.16
- unaffected < 3.16
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/1307028f082756bf453e1889aee9983d30643a4b (opens in a new tab)
- https://git.kernel.org/stable/c/f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e (opens in a new tab)
- https://git.kernel.org/stable/c/72a35070fcefa229b1b031aa7482ad3788e18f07 (opens in a new tab)
- https://git.kernel.org/stable/c/340e0386aa39da181015bee38f309018c335ce16 (opens in a new tab)
- https://git.kernel.org/stable/c/d60de8253c85a02d0e6194b0735e7a562981a04c (opens in a new tab)
- https://git.kernel.org/stable/c/4e7ebfaa0d14cf50e44041bfde38070d6dbc019f (opens in a new tab)
- https://git.kernel.org/stable/c/0d934c934ec746d53fc7e4f53239792647bbae63 (opens in a new tab)
- https://git.kernel.org/stable/c/d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-57041 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68433)Record last updated .