Loading vulnerability…
CVE-2022-4128 is a NULL pointer dereference in the Linux kernel Multipath TCP (MPTCP) implementation. During disconnect processing, MPTCP iterates through and closes subflows in its subflow list. Under conditions involving an MPJ subflow or a passive MPTCP socket, closing a subflow can remove that entry from the list and invalidate the active iterator, leading to a NULL pointer dereference. The upstream fix is included in commit 5c835bb142d4.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux Multipath TCP disconnect-time NULL-pointer dereference.
Linux kernel MPTCP disconnect-time NULL-pointer dereference vulnerability.
A Linux kernel MPTCP NULL-pointer dereference caused by invalidation of the subflow-list iterator during disconnect-time subflow closure, under MPJ-subflow/passive-MPTCP-socket conditions.
A moderate-severity Linux kernel MPTCP NULL-pointer dereference during subflow-list traversal at disconnect time. A local low-privileged user can crash the system, resulting in denial of service.
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.