CVE-2026-80548

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. 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:

s390/vfio_ccw: Selectively expand io_mutex

The io_mutex was defined to serialize the io_regions, but then has also sort of been associated with the I/O themselves because of the close relationship they share.

With the handful of races that are possible, the choices are either to: A) expand the scope of io_mutex to close these remaining windows, or B) reduce the scope of io_mutex to just io_region, and introduce a new lock mechanism for the remaining I/O resources

This patch implements A, since B brings with it a lot more interactions that would need to be tracked and kept in a correct hierarchy. It also takes advantage of the workqueue element for cp_free() that now gets called out of fsm_notoper(), which could be invoked out of an interrupt context and thus cannot acquire a mutex itself.

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
3%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (5)

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

s390/vfio_ccw: Selectively expand io_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

s390/vfio_ccw: Selectively expand io_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

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

s390/vfio_ccw: Selectively expand io_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34f4feff3e90bd09308fad0974e97113b23b812a
generic

s390/vfio_ccw: Selectively expand io_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd
generic

s390/vfio_ccw: Selectively expand io_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a5ac0c0f1f7da33929211a2e41911bf72ee35d8

Vendor Advisories for CVE-2026-80548(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 18× in last 7d / 18× 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 18:31 UTCGHSA enrichment
  3. 2026-08-29 05:18 UTCEG score recompute
  4. 2026-08-29 05:18 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 16:05 UTCGHSA enrichment
  7. 2026-08-28 02:45 UTCEG score recompute
  8. 2026-08-28 02:45 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 13:33 UTCEG score recompute
  11. 2026-08-27 13:33 UTCGHSA enrichment
  12. 2026-08-27 13:00 UTCEG score recompute
  13. 2026-08-27 13:00 UTCGHSA enrichment
  14. 2026-08-27 06:20 UTCEG score recompute 8.80
  15. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  16. 2026-08-26 15:43 UTCNVD update
  17. 2026-08-26 14:43 UTCEG score recompute
  18. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80548?
CVE-2026-80548 is a high vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: s390/vfioccw: Selectively expand iomutex The iomutex was defined to serialize the ioregions, but then has also sort of been associated with the I/O themselves because of the close relationship they share. With the handful of races…
When was CVE-2026-80548 disclosed?
CVE-2026-80548 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80548 actively exploited?
CVE-2026-80548 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80548?
CVE-2026-80548 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-80548?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80548, 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-80548

Explore →

Is Your Infrastructure Affected by CVE-2026-80548?

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