CVE-2023-1074 is a flaw in the Linux kernel Stream Control Transmission Protocol (SCTP) implementation's handling of associations for which no bound address is usable in a requested scope. In the SCTP diagnostic path, inet_diag_msg_sctpasoc_fill() can invoke list_entry() on the next pointer of an empty bound-address list, producing a type-confused pointer while returning association information to userspace. The condition is associated with a memory leak that can be repeatedly triggered to consume kernel resources.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel SCTP address-scope handling vulnerability.
Linux kernel SCTP address-scope handling flaw.
Linux kernel SCTP issue involving unavailable bound addresses for a scope.
Linux kernel SCTP address-scope validation vulnerability.
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.