Loading vulnerability…
CVE-2023-1076 is a Linux kernel TUN/TAP networking vulnerability in socket initialization. Type confusion caused the socket UID (sk_uid) associated with TUN and TAP sockets to be initialized as UID 0 rather than the filesystem UID of the process creating the device. An initial remediation that derived the value from the inode UID was also incorrect. The corrected implementation initializes sk_uid from current_fsuid() in tun_chr_open() and tap_open().
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 TAP device socket UID initialization vulnerability.
Linux kernel TAP driver socket UID initialization vulnerability.
A Linux kernel tun/tap socket UID initialization flaw. An incorrect fix for CVE-2023-1076 could assign an incorrect socket UID, potentially enabling bypass of network filtering or routing decisions, particularly where a non-root user holds CAP_NET_ADMIN.
A Linux kernel tun/tap issue for which the original fixes are described as incorrect. The proposed corrective patches set socket sk_uid using current_fsuid() in tun_chr_open() and tap_open(). The content characterizes the CVE as low impact with CVSS v3 score 5.5.
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.