CVE-2026-68433
Kernel libceph may read uninitialized memory from truncated MON_GET_VERSION_REPLY
Is CVE-2026-68433 being exploited?
Not confirmed. CVE-2026-68433 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-68433?
CVE-2026-68433 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-68433?
Yes. A fix has been recorded for CVE-2026-68433. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68433 affect?
CVE-2026-68433 affects Linux kernel (libceph), Ceph clients/daemons (MON/OSD). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68433?
Apply kernel/libceph updates and restrict Ceph network access until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted Ceph replies can trigger uninitialized kernel memory reads, risking information disclosure or instability via networked Ceph components.
Patch when possible
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < 1307028f082756bf453e1889aee9983d30643a4b
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < 72a35070fcefa229b1b031aa7482ad3788e18f07
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < 340e0386aa39da181015bee38f309018c335ce16
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < d60de8253c85a02d0e6194b0735e7a562981a04c
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < 4e7ebfaa0d14cf50e44041bfde38070d6dbc019f
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < 0d934c934ec746d53fc7e4f53239792647bbae63
- affected>= 513a8243d67f8e8d27f2883bd2f18bc87c7ca376 and < d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0
- affected3.16
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.