vfio/pci: Disable auto-enable of exclusive INTx IRQ
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Disable auto-enable of exclusive INTx IRQ Currently for devices requiring masking at the irqchip for INTx, ie. devices without DisINTx support, the IRQ is enabled in request_irq() and subsequently disabled as necessary to align with the masked status flag. This presents a window where the interrupt could fire between these events, resulting in the IRQ incrementing the disable depth twice. This would be unrecoverable for a user since the masked flag prevents nested enables through vfio. Instead, invert the logic using IRQF_NO_AUTOEN such that exclusive INTx is never auto-enabled, then unmask as required.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in 26389925d6c2126fb777821a0a983adca7ee6351; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in 561d5e1998d58b54ce2bbbb3e843b669aa0b3db5; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in b7a2f0955ffceffadfe098b40b50307431f45438; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in 139dfcc4d723ab13469881200c7d80f49d776060; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in 2a4a666c45107206605b7b5bc20545f8aabc4fa2; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in 3b3491ad0f80d913e7d255941d4470f4a4d9bfda; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in bf0bc84a20e6109ab07d5dc072067bd01eb931ec; From 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 · fixed in fe9a7082684eb059b925c535682e68c34d487d43
- Linux Linux
3.6
- KernelLinux
From 3.6.0 · fixed in 5.4.274; From 5.5.0 · fixed in 5.10.215; From 5.11.0 · fixed in 5.15.154; From 5.16.0 · fixed in 6.1.84; From 6.2.0 · fixed in 6.6.24; From 6.7.0 · fixed in 6.7.12; From 6.8.0 · fixed in 6.8.3
References 8
git.kernel.org
- stable/c/26389925d6c2126fb777821a0a983adca7ee6351
- stable/c/561d5e1998d58b54ce2bbbb3e843b669aa0b3db5
- stable/c/b7a2f0955ffceffadfe098b40b50307431f45438
- stable/c/139dfcc4d723ab13469881200c7d80f49d776060
- stable/c/2a4a666c45107206605b7b5bc20545f8aabc4fa2
- stable/c/3b3491ad0f80d913e7d255941d4470f4a4d9bfda
- stable/c/bf0bc84a20e6109ab07d5dc072067bd01eb931ec
- stable/c/fe9a7082684eb059b925c535682e68c34d487d43