CVE-2026-74684

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3874892dd27d5387aa9a06f58d9060f18f351d24
generic

net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/164c31ee252ebd1ac8f44c2dfc5486b6d9a0379b
generic

net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b444b126cd8e4473e652f529753ed4dd1360a9c
generic

net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15583b07fd691a844fbf7b3ad612cdc9e9a657c0

Vendor Advisories for CVE-2026-74684(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 29× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 04:36 UTCEG score recompute
  2. 2026-08-30 04:36 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 15:29 UTCGHSA enrichment
  5. 2026-08-29 02:22 UTCEG score recompute
  6. 2026-08-29 02:22 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 13:10 UTCGHSA enrichment
  9. 2026-08-28 00:03 UTCEG score recompute
  10. 2026-08-28 00:02 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 10:55 UTCGHSA enrichment
  13. 2026-08-26 21:49 UTCEG score recompute
  14. 2026-08-26 21:49 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 08:40 UTCGHSA enrichment
  17. 2026-08-25 19:34 UTCEG score recompute
  18. 2026-08-25 19:34 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:29 UTCEG score recompute
  21. 2026-08-25 06:29 UTCGHSA enrichment
  22. 2026-08-25 05:55 UTCEG score recompute▲ 7.10
  23. 2026-08-25 05:55 UTCGHSA enrichment
  24. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 7 more
  1. 2026-08-23 13:19 UTCGHSA enrichment
  2. 2026-08-23 13:19 UTCNVD update
  3. 2026-08-23 13:06 UTCGHSA enrichment
  4. 2026-08-23 13:05 UTCMITRE cvelistV5
  5. 2026-08-22 16:24 UTCNVD update
  6. 2026-08-22 15:40 UTCEG score recompute
  7. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74684?
CVE-2026-74684 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net: tap: set skb->dev before parsing virtio net header in tapgetuser_xdp() The commit 4f61f133f354 ("net: tap: NULL pointer derefence in devparseheader_protocol when skb->dev is null") fixed a crash in tapgetuser() by assigning…
When was CVE-2026-74684 disclosed?
CVE-2026-74684 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74684 actively exploited?
CVE-2026-74684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-74684?
CVE-2026-74684 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-74684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74684, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74684

Explore →

Is Your Infrastructure Affected by CVE-2026-74684?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs