CVE-2026-74495

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: 0%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:

igbvf: Fix leak in TX DMA error cleanup

If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb.

Because count is incremented before each frag mapping, it will always match the correct number of unmappings needed when dma_error is reached. Decrementing count before the while loop in dma_error causes an off-by-one error. If any mapping was successful before an unsuccessful mapping, exactly one DMA mapping (the head) would leak.

This bug was introduced by a 2010 fix for an endless loop in dma_error. All other affected drivers have already been fixed.

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
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

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/845a9cdd9b03b7b6fa8de3ee80579780350a7f65
generic

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56726ff12cb6759ab90d6f5332c2377aeca7d249
generic

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31089f4eab42e0fc248ec80c26f9b0bad59ba4cc
generic

igbvf: Fix leak in TX DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0565052b7e2f436b7f1541f4849da96dc0aa7a0e

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

Frequently asked(5)

What is CVE-2026-74495?
CVE-2026-74495 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: igbvf: Fix leak in TX DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented before each frag mapping, it will always…
When was CVE-2026-74495 disclosed?
CVE-2026-74495 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-74495 actively exploited?
CVE-2026-74495 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 61.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74495?
CVE-2026-74495 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74495?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74495, 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-74495

Explore →

Is Your Infrastructure Affected by CVE-2026-74495?

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

Start Free Scan →Browse All CVEs