CVE-2026-74279

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

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

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

crypto: cavium/cpt - fix DMA cleanup using wrong loop index

The sg_cleanup error path used list[i] instead of list[j] when unmapping DMA buffers, leaking successfully mapped entries and repeatedly unmapping the failed one.

CVSS v3
10.0
EG Score
10.0(high)
EG Risk
50(Track)
EG Risk 50/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
Severity100% × 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 17, 2026

Advisory Details (8)

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

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9dbf173bd32d5f81b005008b682bfb50aa093455
generic

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b8a1e1f4e4071a62b20374028744e8cc8310d48
generic

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28141f95ae93b18f9bfde953cb787fcb151fb9da
generic

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23d3a7e896a1fe2d7a6bcb42f093948b79f8a198
generic

crypto: cavium/cpt - fix DMA cleanup using wrong loop index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23c6174e48f66fc10b998b0acdb406cb0caf5c80

Vendor Advisories for CVE-2026-74279(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 46× in last 7d / 46× 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 06:16 UTCGHSA enrichment
  2. 2026-08-21 01:55 UTCEG score recompute
  3. 2026-08-21 01:55 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:34 UTCGHSA enrichment
  6. 2026-08-20 17:14 UTCGHSA enrichment
  7. 2026-08-20 12:48 UTCGHSA enrichment
  8. 2026-08-20 08:27 UTCGHSA enrichment
  9. 2026-08-20 04:06 UTCGHSA enrichment
  10. 2026-08-19 23:45 UTCGHSA enrichment
  11. 2026-08-19 19:24 UTCEG score recompute
  12. 2026-08-19 19:24 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 15:03 UTCGHSA enrichment
  15. 2026-08-19 10:42 UTCGHSA enrichment
  16. 2026-08-19 06:22 UTCGHSA enrichment
  17. 2026-08-19 02:01 UTCGHSA enrichment
  18. 2026-08-18 21:39 UTCGHSA enrichment
  19. 2026-08-18 17:19 UTCEG score recompute
  20. 2026-08-18 17:18 UTCGHSA enrichment
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 12:53 UTCGHSA enrichment
  24. 2026-08-18 08:32 UTCGHSA enrichment
  25. 2026-08-18 04:08 UTCGHSA enrichment
Show 21 more
  1. 2026-08-17 23:46 UTCGHSA enrichment
  2. 2026-08-17 19:25 UTCGHSA enrichment
  3. 2026-08-17 15:04 UTCEG score recompute
  4. 2026-08-17 15:04 UTCGHSA enrichment
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-17 10:43 UTCEG score recompute
  7. 2026-08-17 10:43 UTCGHSA enrichment
  8. 2026-08-17 06:22 UTCEG score recompute
  9. 2026-08-17 06:22 UTCGHSA enrichment
  10. 2026-08-17 05:56 UTCEG score recompute 10.00
  11. 2026-08-17 05:56 UTCGHSA enrichment
  12. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 10 · severity → CRITICAL
  13. 2026-08-17 05:27 UTCEG score recompute
  14. 2026-08-17 05:27 UTCGHSA enrichment
  15. 2026-08-17 05:24 UTCMITRE cvelistV5
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 06:23 UTCNVD update
  20. 2026-08-15 06:17 UTCEG score recompute
  21. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74279?
CVE-2026-74279 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: cavium/cpt - fix DMA cleanup using wrong loop index The sg_cleanup error path used list[i] instead of list[j] when unmapping DMA buffers, leaking successfully mapped entries and repeatedly unmapping the failed one.
When was CVE-2026-74279 disclosed?
CVE-2026-74279 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74279 actively exploited?
CVE-2026-74279 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 57.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74279?
CVE-2026-74279 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-74279?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74279, 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-74279

Explore →

Is Your Infrastructure Affected by CVE-2026-74279?

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