CVE-2026-80633

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.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: 8.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:

iommufd: Take dma_resv lock before dma_buf_unpin() in release path

dma_buf_unpin() requires the caller to hold the exporter's dma_resv lock:

void dma_buf_unpin(struct dma_buf_attachment *attach) { ... dma_resv_assert_held(dmabuf->resv); ... }

iopt_release_pages() calls dma_buf_unpin() without taking that lock, so every iommufd_ioas_destroy()/iommufd_ioas_unmap() that releases the last reference on a DMABUF-backed iopt_pages triggers a WARN. This was hit while running tools/testing/selftests/iommu/iommufd:

WARNING: drivers/dma-buf/dma-buf.c:1137 at dma_buf_unpin+0x62/0x70 RIP: 0010:dma_buf_unpin+0x62/0x70 Call Trace: dma_buf_unpin+0x62/0x70 iopt_release_pages+0xe4/0x190 iopt_unmap_iova_range+0x1c7/0x290 iopt_unmap_all+0x1a/0x30 iommufd_ioas_destroy+0x1d/0x50 iommufd_fops_release+0x93/0x150 __fput+0xfc/0x2c0 __x64_sys_close+0x3d/0x80 do_syscall_64+0x65/0x180

Take the dma_resv lock around dma_buf_unpin() in iopt_release_pages(), matching the iopt_map_dmabuf() convention. dma_buf_detach() acquires the reservation lock internally, so it must remain outside the locked region.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (2)

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

iommufd: Take dma_resv lock before dma_buf_unpin() in release path - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommufd: Take dma_resv lock before dma_buf_unpin() in release path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc69d0332421fd2943b66dbe5e597bf4fd5af126

Vendor Advisories for CVE-2026-80633(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 12× in last 7d / 12× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 20:19 UTCEG score recompute
  3. 2026-08-29 20:18 UTCGHSA enrichment
  4. 2026-08-29 07:27 UTCEG score recompute
  5. 2026-08-29 07:27 UTCGHSA enrichment
  6. 2026-08-29 06:37 UTCEG score recompute▲ 8.80
  7. 2026-08-29 06:36 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:34 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80633?
CVE-2026-80633 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: iommufd: Take dmaresv lock before dmabuf_unpin() in release path dmabufunpin() requires the caller to hold the exporter's dma_resv lock: void dmabufunpin(struct dmabufattachment *attach) { ... dmaresvassert_held(dmabuf->resv); ...…
When was CVE-2026-80633 disclosed?
CVE-2026-80633 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80633 actively exploited?
CVE-2026-80633 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 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80633?
CVE-2026-80633 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-80633?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80633, 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-80633

Explore →

Is Your Infrastructure Affected by CVE-2026-80633?

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

Start Free Scan →Browse All CVEs