Loading vulnerability…
A Linux kernel networking flaw allows a packet socket created without a device binding in one network namespace to register packet-type state that is visible through the procfs packet-type listing to users in other network namespaces. Packet-socket state is intended to be network-namespace aware, but the associated packet_type structure did not retain or validate its originating network namespace during listing. The upstream fix records the relevant network namespace in packet_type entries and filters entries during ptype_seq_show.
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 kernel information-disclosure flaw through /proc/net/ptype.
A low-severity Linux kernel information-disclosure vulnerability involving leakage of information through /proc/net/ptype.
A local Linux kernel network-namespace isolation flaw in /proc/net/ptype. An unbound packet socket's packet_type can be exposed across network namespaces, resulting in information disclosure. Red Hat rates its impact Low (CVSS 3.3), while NVD lists CVSS 7.1.
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.