CVE-2026-74684

net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp()

HIGH
7.1
CVSS Score
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 21, 2026 at 01:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() The commit 4f61f133f354 ("net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null") fixed a crash in tap_get_user() by assigning skb->dev before calling tun_vnet_hdr_to_skb(). This is required because virtio_net_hdr_to_skb() may invoke dev_parse_header_protocol(), which dereferences skb->dev. Without the assignment, a NULL pointer dereference can occur. However, tap_get_user_xdp() still parses the virtio-net header before assigning skb->dev. When the vhost TX path passes an XDP buffer containing a GSO virtio-net header but the protocol is set to zero on purpose, tun_vnet_hdr_to_skb() can reach dev_parse_header_protocol() while skb->dev is still NULL, resulting in a crash. Fix this by looking up the tap device and assigning skb->dev before calling tun_vnet_hdr_to_skb(), matching the ordering already used in tap_get_user(). Preserve the existing RCU read-side critical section across dev_queue_xmit().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.2264.19.1815.10.245.11.75.125.4.10654ef8243c3c8e90f1ea5792e6752e021a25c8eb3924a9bc362a5223cd448ca08c3dde21235adc31099b1d3f74b9ef72c2f74c8e4c078e1bc0706e748ca278267d6cd9544645731732455b6b20cb0e895ea3fb2ce5fa794d02135f5c079e05cd6fc3f545dfaa3baa2828c5e1c4374f3e60041f75c64f5fcb6
Vendor states this is fixed in 15583b07fd691a844fbf7b3ad612cdc9e9a657c0 (fixed)
Vendor states this is fixed in 164c31ee252ebd1ac8f44c2dfc5486b6d9a0379b (fixed)
Vendor states this is fixed in 3874892dd27d5387aa9a06f58d9060f18f351d24 (fixed)
Vendor states this is fixed in 8b444b126cd8e4473e652f529753ed4dd1360a9c (fixed)
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.12 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card