CVE-2026-74474

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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 — 4 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: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

vxlan: use pskb_network_may_pull() for transmit path header pulls

In vxlan_xmit(), arp_reduce(), and vxlan_mdb_entry_skb_get(), pskb_may_pull() was being called to verify the availability of network layer headers (ARP, IPv6/ND, IP/IPv6 MDB keys).

However, during transmit skb->data points to the MAC header, so skb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, len) only checks len bytes from skb->data rather than skb_network_offset(skb) + len, which can leave part of the network header in non-linear frags.

Replace these remaining pskb_may_pull() calls with pskb_network_may_pull() to properly account for the MAC header offset.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

September 14, 2026

Advisory Details (6)

Auto-updated Sep 28, 2026
Patch available.
generic

vxlan: use pskb_network_may_pull() for transmit path header pulls - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: use pskb_network_may_pull() for transmit path header pulls - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: use pskb_network_may_pull() for transmit path header pulls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94dee751aad627b3645d424b5d0c736d394573e9
generic

vxlan: use pskb_network_may_pull() for transmit path header pulls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7076a34b6e33315dc160b4612bfea1c597495585
generic

vxlan: use pskb_network_may_pull() for transmit path header pulls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6146901881f09ef063eb34ad389f63231f8486f5
generic

vxlan: use pskb_network_may_pull() for transmit path header pulls - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/371425d4be7795e9158388af9eee0201e6047410

Vendor Advisories for CVE-2026-74474(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (165 versions)
  • every version up to 7.1.8-1: fixed in 7.1.8-1
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 55× in last 7d / 253× 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.

Showing the most recent 100 of 409 total refreshes for this CVE.

  1. 2026-10-05 06:45 UTCVendor advisory
  2. 2026-10-05 06:45 UTCGHSA enrichment
  3. 2026-10-05 02:23 UTCEG score recompute
  4. 2026-10-05 02:23 UTCVendor advisory
  5. 2026-10-05 02:23 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 21:56 UTCVendor advisory
  8. 2026-10-04 21:56 UTCGHSA enrichment
  9. 2026-10-04 16:27 UTCVendor advisory
  10. 2026-10-04 16:27 UTCGHSA enrichment
  11. 2026-10-04 12:02 UTCVendor advisory
  12. 2026-10-04 12:02 UTCGHSA enrichment
  13. 2026-10-04 07:39 UTCVendor advisory
  14. 2026-10-04 07:39 UTCGHSA enrichment
  15. 2026-10-04 03:24 UTCVendor advisory
  16. 2026-10-04 03:24 UTCGHSA enrichment
  17. 2026-10-03 19:29 UTCEG score recompute
  18. 2026-10-03 19:29 UTCVendor advisory
  19. 2026-10-03 19:29 UTCGHSA enrichment
  20. 2026-10-03 14:26 UTCEPSS rescore
  21. 2026-10-03 02:00 UTCVendor advisory
  22. 2026-10-03 02:00 UTCGHSA enrichment
  23. 2026-10-02 21:45 UTCEG score recompute
  24. 2026-10-02 21:45 UTCVendor advisory
  25. 2026-10-02 21:45 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 15:51 UTCVendor advisory
  2. 2026-10-02 15:50 UTCGHSA enrichment
  3. 2026-10-02 07:02 UTCVendor advisory
  4. 2026-10-02 07:02 UTCGHSA enrichment
  5. 2026-10-02 02:00 UTCEG score recompute
  6. 2026-10-02 02:00 UTCVendor advisory
  7. 2026-10-02 02:00 UTCGHSA enrichment
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 14:25 UTCVendor advisory
  10. 2026-10-01 14:25 UTCGHSA enrichment
  11. 2026-10-01 10:05 UTCVendor advisory
  12. 2026-10-01 10:05 UTCGHSA enrichment
  13. 2026-10-01 05:50 UTCVendor advisory
  14. 2026-10-01 05:50 UTCGHSA enrichment
  15. 2026-10-01 01:33 UTCVendor advisory
  16. 2026-10-01 01:33 UTCGHSA enrichment
  17. 2026-09-30 20:57 UTCEG score recompute
  18. 2026-09-30 20:57 UTCVendor advisory
  19. 2026-09-30 20:57 UTCGHSA enrichment
  20. 2026-09-29 15:24 UTCEPSS rescore
  21. 2026-09-29 08:18 UTCVendor advisory
  22. 2026-09-29 08:18 UTCGHSA enrichment
  23. 2026-09-29 03:54 UTCVendor advisory
  24. 2026-09-29 03:54 UTCGHSA enrichment
  25. 2026-09-28 23:38 UTCEG score recompute
  26. 2026-09-28 23:38 UTCVendor advisory
  27. 2026-09-28 23:38 UTCGHSA enrichment
  28. 2026-09-28 13:52 UTCEPSS rescore
  29. 2026-09-28 11:23 UTCVendor advisory
  30. 2026-09-28 11:23 UTCGHSA enrichment
  31. 2026-09-28 07:07 UTCVendor advisory
  32. 2026-09-28 07:07 UTCGHSA enrichment
  33. 2026-09-28 02:52 UTCVendor advisory
  34. 2026-09-28 02:52 UTCGHSA enrichment
  35. 2026-09-27 22:37 UTCVendor advisory
  36. 2026-09-27 22:37 UTCGHSA enrichment
  37. 2026-09-27 16:56 UTCEG score recompute
  38. 2026-09-27 16:56 UTCVendor advisory
  39. 2026-09-27 16:55 UTCGHSA enrichment
  40. 2026-09-27 13:48 UTCEPSS rescore
  41. 2026-09-27 12:40 UTCVendor advisory
  42. 2026-09-27 12:40 UTCGHSA enrichment
  43. 2026-09-27 08:25 UTCEG score recompute
  44. 2026-09-27 08:25 UTCVendor advisory
  45. 2026-09-27 08:25 UTCGHSA enrichment
  46. 2026-09-26 15:59 UTCEPSS rescore
  47. 2026-09-26 00:28 UTCEPSS rescore
  48. 2026-09-25 11:53 UTCVendor advisory
  49. 2026-09-25 11:53 UTCGHSA enrichment
  50. 2026-09-25 06:44 UTCVendor advisory
  51. 2026-09-25 06:44 UTCGHSA enrichment
  52. 2026-09-25 02:28 UTCEG score recompute
  53. 2026-09-25 02:28 UTCVendor advisory
  54. 2026-09-25 02:28 UTCGHSA enrichment
  55. 2026-09-24 14:04 UTCEPSS rescore
  56. 2026-09-24 13:33 UTCVendor advisory
  57. 2026-09-24 13:33 UTCGHSA enrichment
  58. 2026-09-24 09:17 UTCVendor advisory
  59. 2026-09-24 09:17 UTCGHSA enrichment
  60. 2026-09-24 05:02 UTCVendor advisory
  61. 2026-09-24 05:02 UTCGHSA enrichment
  62. 2026-09-24 00:47 UTCVendor advisory
  63. 2026-09-24 00:46 UTCGHSA enrichment
  64. 2026-09-23 20:31 UTCEG score recompute
  65. 2026-09-23 20:31 UTCVendor advisory
  66. 2026-09-23 20:31 UTCGHSA enrichment
  67. 2026-09-23 17:54 UTCEPSS rescore
  68. 2026-09-23 13:49 UTCVendor advisory
  69. 2026-09-23 13:49 UTCGHSA enrichment
  70. 2026-09-23 09:33 UTCVendor advisory
  71. 2026-09-23 09:33 UTCGHSA enrichment
  72. 2026-09-23 05:17 UTCVendor advisory
  73. 2026-09-23 05:17 UTCGHSA enrichment
  74. 2026-09-23 01:02 UTCVendor advisory
  75. 2026-09-23 01:02 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74474?
CVE-2026-74474 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskbnetworkmay_pull() for transmit path header pulls In vxlanxmit(), arpreduce(), and vxlanmdbentryskbget(), pskbmaypull() was being called to verify the availability of network layer headers (ARP, IPv6/ND, IP/IPv6 MDB…
When was CVE-2026-74474 disclosed?
CVE-2026-74474 was first published on August 15, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74474 actively exploited?
CVE-2026-74474 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74474?
CVE-2026-74474 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74474?
A fix for CVE-2026-74474 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74474 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74474

Explore →

Is Your Infrastructure Affected by CVE-2026-74474?

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

Book a Demo →Browse All CVEs