CVE-2026-74473

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: 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:

vxlan: use pskb_network_may_pull() in route_shortcircuit()

route_shortcircuit() currently calls pskb_may_pull(skb, sizeof(struct iphdr)) (or ipv6hdr), which checks if bytes are available starting from skb->data.

However, in vxlan_xmit(), skb->data points to the MAC header, so skb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, 20) only checks 20 bytes from skb->data (which is 14 bytes MAC header + 6 bytes of IP header), leaving the rest of the IP header potentially un-pulled in non-linear frags. Subsequent dereferences of ip_hdr(skb)->daddr can read beyond the pulled linear buffer length.

Fix this by using pskb_network_may_pull(), which adds skb_network_offset(skb) to the length check to ensure the full network header is present in the linear buffer.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (8)

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

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ee799977d7941dbfb11049e17edd9eaf4f8820f7
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c419af4924c1593500a40519730ed98575d04a3e
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aa0d31376d574ac858a40078431a77127bf04ee4
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6bd0a3a1b5744166946f0c551a6665c3b46b05e4
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f3f96e771a20263635bb5e1307c112d613b4bbd
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42887be7c4cf283cce02cd0fb6411221167c8b6c
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26bb2dd0a8839617e2c79ffbbe1923f8e4bab9fb
generic

vxlan: use pskb_network_may_pull() in route_shortcircuit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/214ba43faf106cb06cd3dd30999c5c809c868b53

Vendor Advisories for CVE-2026-74473(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 48× in last 7d / 48× 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-21 07:54 UTCGHSA enrichment
  2. 2026-08-21 03:39 UTCGHSA enrichment
  3. 2026-08-20 23:24 UTCEG score recompute
  4. 2026-08-20 23:24 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 19:10 UTCGHSA enrichment
  7. 2026-08-20 14:55 UTCGHSA enrichment
  8. 2026-08-20 10:40 UTCGHSA enrichment
  9. 2026-08-20 06:25 UTCGHSA enrichment
  10. 2026-08-20 02:09 UTCGHSA enrichment
  11. 2026-08-19 21:52 UTCGHSA enrichment
  12. 2026-08-19 17:36 UTCEG score recompute
  13. 2026-08-19 17:36 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 16:45 UTCEG score recompute
  16. 2026-08-19 16:45 UTCGHSA enrichment
  17. 2026-08-19 14:53 UTCGHSA enrichment
  18. 2026-08-19 10:38 UTCGHSA enrichment
  19. 2026-08-19 06:19 UTCGHSA enrichment
  20. 2026-08-19 01:52 UTCGHSA enrichment
  21. 2026-08-18 21:37 UTCGHSA enrichment
  22. 2026-08-18 17:00 UTCEG score recompute
  23. 2026-08-18 16:59 UTCGHSA enrichment
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 13:49 UTCEPSS rescore
Show 23 more
  1. 2026-08-18 12:24 UTCGHSA enrichment
  2. 2026-08-18 08:02 UTCGHSA enrichment
  3. 2026-08-18 03:44 UTCGHSA enrichment
  4. 2026-08-17 23:29 UTCGHSA enrichment
  5. 2026-08-17 19:12 UTCGHSA enrichment
  6. 2026-08-17 14:55 UTCEG score recompute
  7. 2026-08-17 14:55 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 10:40 UTCEG score recompute
  10. 2026-08-17 10:40 UTCGHSA enrichment
  11. 2026-08-17 06:25 UTCEG score recompute
  12. 2026-08-17 06:25 UTCGHSA enrichment
  13. 2026-08-17 05:55 UTCEG score recompute▲ 9.80
  14. 2026-08-17 05:55 UTCGHSA enrichment
  15. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  16. 2026-08-17 05:25 UTCEG score recompute
  17. 2026-08-17 05:25 UTCGHSA enrichment
  18. 2026-08-17 05:24 UTCMITRE cvelistV5
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-15 13:27 UTCNVD update
  22. 2026-08-15 12:40 UTCEG score recompute
  23. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74473?
CVE-2026-74473 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskbnetworkmaypull() in routeshortcircuit() routeshortcircuit() currently calls pskbmay_pull(skb, sizeof(struct iphdr)) (or ipv6hdr), which checks if bytes are available starting from skb->data. However, in vxlan_xmit(),…
When was CVE-2026-74473 disclosed?
CVE-2026-74473 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74473 actively exploited?
CVE-2026-74473 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74473?
CVE-2026-74473 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74473?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74473, 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-74473

Explore →

Is Your Infrastructure Affected by CVE-2026-74473?

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

Start Free Scan →Browse All CVEs