Loading vulnerability…
CVE-2026-63887 is a heap-based buffer overflow in the Linux kernel LIO iSCSI target implementation. The flaw is in iscsi_encode_text_output(), which appends iSCSI login text records in the form "key=value\0" into a fixed-size 8192-byte response buffer allocated during login setup. Multiple sprintf() call sites in this function append encoded records without checking remaining capacity. Although the login request payload is bounded, an attacker can supply a single crafted Login PDU containing many minimal key/value pairs that cause the target to generate substantially larger response records for unknown keys. In the described case, up to 2048 minimal input pairs can expand into approximately 32 KiB of output written into an 8 KiB heap buffer, resulting in an approximately 24 KiB overwrite in the kmalloc-8k slab. The issue is reachable before authentication during iSCSI login handling in both the security and operational negotiation phases, making it a pre-authentication memory corruption vulnerability with potential remote code execution implications in kernel context.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.