CVE-2026-45843 is an out-of-bounds read vulnerability in the Linux kernel SLIP subsystem, specifically in the VJ-compressed TCP header decompression path handled by slhc_uncompress(). The vulnerable code advances through compressed packet data using the helpers decode() and pull16(), but those helpers did not properly enforce bounds against the compressed packet length. In addition, decode() masked its return value with & 0xffff, which prevented it from ever returning -1 as intended by callers, leaving existing error-handling paths effectively dead code. A crafted short compressed frame whose change byte requests optional fields can cause decode() to read past the end of the packet buffer. The over-read bytes may then be incorporated into the cached connection state (cstate) and reflected into subsequently reconstructed packets. The fix changes decode() and pull16() to take a packet end pointer and return -1 when packet data is exhausted, and adds an explicit bounds check before reading the TCP checksum.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.