Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80620: Revert "PCI/MSI: Unmap MSI-X region on error"

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0a2aeb02894b839ecc3ece6dc7e5c3d6c3def16f, 3691a82be2095abaf3326a1cbf7b25858a1d959c, 6.1.178.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0a2aeb02894b839ecc3ece6dc7e5c3d6c3def16f, 3691a82be2095abaf3326a1cbf7b25858a1d959c, 6.1.178 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: Revert "PCI/MSI: Unmap MSI-X region on error" This reverts commit 1a8d4c6ecb4c81261bcdf13556abd4a958eca202. Commit 1a8d4c6ecb4c ("PCI/MSI: Unmap MSI-X region on error") added an iounmap(dev->msix_base) on the error path of msix_capability_init() to release the MSI-X region when msix_setup_interrupts() fails. When msix_setup_interrupts() fails, the call chain is: msix_setup_interrupts() -> __msix_setup_interrupts() struct pci_dev *dev __free(free_msi_irqs) = __dev; ... return ret; // __free cleanup fires on error The __free(free_msi_irqs) cleanup calls pci_free_msi_irqs(), which already handles the unmap: void pci_free_msi_irqs(struct pci_dev *dev) { pci_msi_teardown_msi_irqs(dev); if (dev->msix_base) { iounmap(dev->msix_base); // already unmapped here dev->msix_base = NULL; // and set to NULL } } So dev->msix_base is unmapped and set to NULL before msix_setup_interrupts() returns to msix_capability_init(). The "goto out_unmap" introduced by commit 1a8d4c6ecb4c ("PCI/MSI: Unmap MSI-X region on error") then calls iounmap() a second time on a NULL pointer. This was reproduced on Intel Emerald Rapids (192 CPUs) while running tools/testing/selftests/kexec/test_kexec_jump.sh: WARNING: CPU#44 at iounmap+0x2a/0xe0 RIP: 0010:iounmap+0x2a/0xe0 RDI: 0000000000000000 Call Trace: msix_capability_init+0x317/0x3f0 __pci_enable_msix_range+0x21d/0x2c0 pci_alloc_irq_vectors_affinity+0xa9/0x130 nvme_setup_io_queues+0x2a8/0x420 [nvme] nvme_reset_work+0x151/0x340 [nvme] ... RDI=0 confirms iounmap() is called with NULL. Restore the original "goto out_disable" and leave the unmap to the existing __free(free_msi_irqs) cleanup.

Published
Aug 28, 2026
Updated
Nov 6, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80620

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 19bf27b450fcd5309bacd614b12bd7de1ac6535b, 7.0affected
    • 4a7589b615a3db6792d36b874add86cd22188c95 and later · before 82e120a7dd566c476ba923d30e3fb78e8118a1ddaffected · git
    • 5f007c6acaa7d9a543b492c1e48c48a0ea1d7147 and later · before 6848ca381edff84f87dd1b6973848c271541e813affected · git
    • 76f7abd4ee0188f06465bdd3c053fdc5e8595152 and later · before 0a2aeb02894b839ecc3ece6dc7e5c3d6c3def16faffected · git
    • aee8db5f048616990dbdefcc25689ade0a2620ec and later · before f79519f636059b007d6abc91652f36dea4f54a20affected · git
    • 1a8d4c6ecb4c81261bcdf13556abd4a958eca202 and later · before 3691a82be2095abaf3326a1cbf7b25858a1d959caffected · git
    • 1a8d4c6ecb4c81261bcdf13556abd4a958eca202 and later · before f64e03da0d83cb173743888bff4a7e61476a8fc2affected · git
    • 6.1.165 and later · before 6.1.178affected · semver
    • 6.6.128 and later · before 6.6.145affected · semver
    • 6.12.75 and later · before 6.12.97affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80615Aug 28, 2026 · net: dst_metadata: fix false-positive memcpy overflow in tun_dst_unclone
    32Monitor
  • ← EarlierCVE-2026-80616Aug 28, 2026 · ieee802154: Avoid calling WARN_ON() on -ENOMEM in cfg802154_switch_netns()
    0Monitor
  • Later →CVE-2026-80622Aug 28, 2026 · char: tlclk: fix use-after-free in tlclk_cleanup()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0a2aeb02894b839ecc3ece6dc7e5c3d6c3def16fVendor (CNA)
Linux Linux3691a82be2095abaf3326a1cbf7b25858a1d959cVendor (CNA)
Linux Linux6.1.178Vendor (CNA)
Linux Linux6.12.97Vendor (CNA)
Linux Linux6.18.40Vendor (CNA)
Linux Linux6.20Vendor (CNA)
Linux Linux6.6.145Vendor (CNA)
Linux Linux6848ca381edff84f87dd1b6973848c271541e813Vendor (CNA)
Linux Linux82e120a7dd566c476ba923d30e3fb78e8118a1ddVendor (CNA)
Linux Linuxf64e03da0d83cb173743888bff4a7e61476a8fc2Vendor (CNA)
Linux Linuxf79519f636059b007d6abc91652f36dea4f54a20Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records