Loading vulnerability…
CVE-2026-45842 is a Linux kernel vulnerability in the SLIP/PPP Van Jacobson (VJ) compression receive path. The flaw exists because slhc_init() accepts rslots == 0 as a valid configuration meaning no receive compression, but receive-side helpers do not safely handle that state. When initialized this way, struct slcompress is allocated with comp->rstate left NULL and comp->rslot_limit left 0. Subsequent receive processing in slhc_uncompress() may dereference comp->rstate[x] when a VJ header carries an explicit connection ID, and slhc_remember() may compute &comp->rstate[...] after only checking the packet slot number against comp->rslot_limit. Because rslot_limit is 0, slot 0 passes the range check and causes a NULL pointer dereference. The vulnerable configuration is reachable through PPP: PPPIOCSMAXCID stores its argument in a signed int, and a value such as 0xffff0000 sign-extends to -1 via arithmetic right shift, causing val2 + 1 to become 0 and leading ppp_generic.c to call slhc_init(0, 1). Once this malformed VJ state is installed, inbound VJ-compressed or VJ-uncompressed frames selecting slot 0 can crash the kernel in softirq 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.
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.