CVE-2026-68433

HIGHCVSS 8.6/10EPSS 0.28%

Last modified

CVE-2026-68433 is a high-severity vulnerability rated 8.6/10 on the CVSS scale. 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.. EPSS estimates a 0.28% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.28%

20.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 1307028f082756bf453e1889aee9983d30643a4b; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 72a35070fcefa229b1b031aa7482ad3788e18f07; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 340e0386aa39da181015bee38f309018c335ce16; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < d60de8253c85a02d0e6194b0735e7a562981a04c; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 4e7ebfaa0d14cf50e44041bfde38070d6dbc019f; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < 0d934c934ec746d53fc7e4f53239792647bbae63; >= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, < d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0
LinuxLinux3.16

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68433?
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.
How severe is CVE-2026-68433?
CVE-2026-68433 has a CVSS score of 8.6/10 (HIGH severity). The EPSS model estimates a 0.28% probability of exploitation in the next 30 days.
How do I fix CVE-2026-68433?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68433?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST