CVE-2023-52628 is a stack out-of-bounds write in the Linux kernel netfilter nftables extended-header expression handling. When the expression length is a multiple of four bytes, the cleanup operation that clears a partial register remainder writes one 32-bit element beyond the destination stack array. The cleanup is only needed for lengths that are not aligned to the register size, but was performed unconditionally. The flaw originated during the Linux 4.1 development cycle and was inherited by extended-header support for TCP, SCTP, and IP options.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A 4-byte stack out-of-bounds write vulnerability in the Linux kernel Netfilter nftables exthdr handling.
A 4-byte stack out-of-bounds write vulnerability in the Linux kernel netfilter nftables exthdr functionality.
A Linux kernel Netfilter/nftables exthdr vulnerability involving a 4-byte stack out-of-bounds write.
A Linux kernel Netfilter nftables exthdr vulnerability involving a 4-byte out-of-bounds stack write.
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.