CVE-2026-74280

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM 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 — 4 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: 0.8%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

crypto: marvell/octeontx - fix DMA cleanup using wrong loop index

The sg_cleanup 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.0CRITICALmedium confidence
EG Risk
50
EG Risk 50/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
Severity100% × 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.8%
EPSS %ILE
53rd
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

August 17, 2026

Advisory Details (8)

Auto-updated Oct 5, 2026
Patch available.
generic

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

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

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

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

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

https://git.kernel.org/stable/c/97f150ba3e372256eabb93bd80c2cf3740077fb5
generic

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

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

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

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

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

https://git.kernel.org/stable/c/7891c64c0520519782470ba29bac8a5761e295d8
generic

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

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

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

https://git.kernel.org/stable/c/5f99a396f706afc749448659d1565991330e4f71

Vendor Advisories for CVE-2026-74280(1)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 51× in last 7d / 243× 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 400 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-74280?
CVE-2026-74280 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: marvell/octeontx - fix DMA cleanup using wrong loop index The sg_cleanup 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-74280 disclosed?
CVE-2026-74280 was first published 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-74280 actively exploited?
CVE-2026-74280 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74280?
CVE-2026-74280 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74280?
A fix for CVE-2026-74280 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74280 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-74280

Explore →

Is Your Infrastructure Affected by CVE-2026-74280?

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