Loading vulnerability…
CVE-2024-27013 is an uncontrolled resource-consumption vulnerability in the Linux kernel TUN network-device driver. When the TUN receive path processes illegal packets, tun_do_read() can repeatedly emit hexadecimal packet dumps. A vhost worker may invoke this path while receiving packets. Under sustained malformed or otherwise illegal packet input, excessive console logging consumes substantial CPU time, particularly when a console is enabled, and can trigger soft-lockup detection. The fix rate-limits logging through the kernel net_ratelimit mechanism.
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.
3 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.
A Linux kernel TUN-device issue in which receiving illegal packets could cause excessive logging; the resolution rate-limits printing for such packets.
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.