CVE-2024-27013 is an uncontrolled resource-consumption vulnerability in the Linux kernel TUN network-device component. When TUN receives illegal packets through callbacks invoked by a vhost worker, the tun_do_read path repeatedly emits hexadecimal packet dumps without rate limiting. A sustained stream of malformed packets can cause excessive kernel logging activity. The upstream fix applies the kernel net_ratelimit mechanism to limit the rate of these diagnostic messages.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel TUN device excessive logging denial-of-service flaw.
Linux kernel TUN device flaw involving handling of illegal packets and unrestricted diagnostic-message printing.
Unknown
Unknown
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.