CVE-2026-23136 affects sparse-read reply handling in the Linux kernel libceph OSD client. Sparse-read progress is tracked by a state machine largely independent of the messenger state. When a connection is lost during a reply payload or the sparse-read state machine returns an error, fault recovery reconnects and retries pending operations without resetting sparse-read state. Consequently, the client can interpret the beginning of a new reply as a continuation of the previous reply, potentially entering an unrecoverable failure loop. The fix resets sparse-read state in osd_fault() before operations are retried.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability covered by Oracle Linux kernel update ELSA-2026-71602; individual technical details and exploit availability are not specified.
Listed in an AlmaLinux 10 kernel security advisory referencing RHSA-2026:71602. Individual vulnerability details are not provided; exploit availability is stated at the advisory level.
Denial-of-service vulnerability in the Linux kernel libceph OSD client caused by an unreset sparse-read state.
A Linux kernel denial-of-service vulnerability in the libceph OSD client caused by an unreset sparse-read state.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.