Loading vulnerability…
CVE-2023-4194 is an improper access-control flaw in the Linux kernel TUN/TAP implementation. The original fixes for CVE-2023-1076 incorrectly or incompletely initialize a TUN/TAP socket UID: the affected changes pass inode->i_uid to sock_init_data_uid(), although that value is not accurate. This incorrect ownership association can undermine network filtering decisions.
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/TAP socket-UID initialization flaw enabling local network-filter bypass.
Linux kernel TAP socket UID initialization vulnerability.
Linux kernel TAP driver socket UID initialization 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.