CVE-2026-80720

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

iomap: add a separate bio_set for iomap_split_ioend

iomap_split_ioend can split bios that already come from iomap_ioend_bioset and thus deadlock when the bioset is exhausted.

Add a separate bio_set to avoid this deadlock.

Christian Brauner says: Mark iomap_ioend_split_bioset static as it is only used in ioend.c, fixing the sparse warning reported by the kernel test robot.

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

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (3)

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

iomap: add a separate bio_set for iomap_split_ioend - kernel/git/stable/linux.git - Linux kernel stable tree

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

iomap: add a separate bio_set for iomap_split_ioend - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a869be56e9f6ce7462abcf324ebdefc5de051be
generic

iomap: add a separate bio_set for iomap_split_ioend - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-80720(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 14× in last 7d / 14× 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 05:43 UTCEG score recompute
  2. 2026-08-30 05:43 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 18:35 UTCEG score recompute
  5. 2026-08-29 18:35 UTCGHSA enrichment
  6. 2026-08-29 07:25 UTCEG score recompute
  7. 2026-08-29 07:24 UTCGHSA enrichment
  8. 2026-08-29 06:35 UTCEG score recompute 7.50
  9. 2026-08-29 06:35 UTCGHSA enrichment
  10. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 08:20 UTCNVD update
  13. 2026-08-28 07:33 UTCEG score recompute
  14. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80720?
CVE-2026-80720 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: iomap: add a separate bioset for iomapsplit_ioend iomapsplitioend can split bios that already come from iomapioendbioset and thus deadlock when the bioset is exhausted. Add a separate bio_set to avoid this deadlock. Christian…
When was CVE-2026-80720 disclosed?
CVE-2026-80720 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-80720 actively exploited?
CVE-2026-80720 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-80720?
CVE-2026-80720 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-80720?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80720, 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-80720

Explore →

Is Your Infrastructure Affected by CVE-2026-80720?

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