CVE-2026-80620: Linux kernel · Revert "PCI/MSI: Unmap MSI-X region on error
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f79519f636059b007d6abc91652f36dea4f54a20 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:47 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in f79519f636059b007d6abc91652f36dea4f54a20, f64e03da0d83cb173743888bff4a7e61476a8fc2, 6848ca381edff84f87dd1b6973848c271541e813 +8
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied by reverting the problematic commit that introduced the double unmap. Users should update to the fixed Linux kernel versions listed in the established facts to resolve this issue. No additional mitigation actions are required beyond applying the official fix.
Description
CVE-2026-80620 is a vulnerability in the Linux kernel related to improper handling of MSI-X region unmapping on error paths. A recent commit introduced a double unmap of the MSI-X region by calling iounmap() on a NULL pointer, causing a kernel warning and potential instability. The issue occurs during MSI-X interrupt setup failure cleanup, where the MSI-X region is unmapped twice. This has been observed on Intel Emerald Rapids CPUs during kernel self-tests. The fix reverts the problematic commit to restore the original error handling flow.
References
- git.kernel.org/stable/c/82e120a7dd566c476ba923d30e3fb78e8118a1dd (opens in a new tab)
- git.kernel.org/stable/c/6848ca381edff84f87dd1b6973848c271541e813 (opens in a new tab)
- git.kernel.org/stable/c/0a2aeb02894b839ecc3ece6dc7e5c3d6c3def16f (opens in a new tab)
- git.kernel.org/stable/c/f79519f636059b007d6abc91652f36dea4f54a20 (opens in a new tab)
- git.kernel.org/stable/c/3691a82be2095abaf3326a1cbf7b25858a1d959c (opens in a new tab)
- git.kernel.org/stable/c/f64e03da0d83cb173743888bff4a7e61476a8fc2 (opens in a new tab)