Loading vulnerability…
CVE-2026-22984 is a Linux kernel vulnerability in the libceph component caused by insufficient bounds validation in handle_auth_done(). The flaw arises because payload_len was not explicitly checked before data was accessed in a callout path, creating a condition where malformed or unexpected authentication payload data could trigger an out-of-bounds read. The issue was resolved by adding an explicit bounds check on payload_len before the affected access. The vulnerability affects the kernel Ceph client authentication handling path and can expose kernel memory safety to attacker-controlled or corrupted input from the Ceph protocol flow.
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.
Linux kernel libceph out-of-bounds read vulnerability in handle_auth_done().
A Linux kernel libceph out-of-bounds read vulnerability in handle_auth_done().
A Linux kernel libceph out-of-bounds read vulnerability in handle_auth_done().
Linux kernel libceph vulnerability involving potential out-of-bounds reads in handle_auth_done().
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.