CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw affects a narrow virtualization/device-passthrough path. A race in VFIO PCI interrupt handling can leave an interrupt permanently disabled for the user, disrupting the assigned device. Sources do not provide CVSS, confirmed exploitation, or broad remote attack evidence.
Executive priority
Treat as a targeted infrastructure maintenance issue, not an emergency internet-wide exposure from the provided evidence. Prioritize virtualization hosts and embedded products that use Linux VFIO PCI passthrough, then follow normal kernel patch governance.
Technical view
The bug is in vfio/pci exclusive INTx handling for devices without DisINTx support. request_irq() could briefly auto-enable the IRQ before VFIO reconciled masked state, allowing an interrupt to fire and double-increment disable depth. The fix uses IRQF_NO_AUTOEN so exclusive INTx is not auto-enabled before explicit unmasking.
Likely exposure
Likely exposure is Linux hosts running affected kernels with VFIO PCI device passthrough, especially devices using legacy INTx interrupts and requiring irqchip masking. General Linux servers without VFIO PCI passthrough are less likely to be practically exposed based on the provided description.
Exploitation context
CISA KEV status is false in the bundle, and no cited source states active exploitation. The source material describes a kernel race and stability/availability impact, not a public exploit path or remote unauthenticated attack.
Researcher notes
The affected-version data is sparse and partly commit-based. Validate against vendor backports rather than raw upstream version strings alone. The operational impact appears tied to an unrecoverable IRQ disable-depth mismatch for specific INTx passthrough devices.
Mitigation direction
Update to a vendor kernel containing the referenced stable VFIO PCI fixes.
Use distro advisories, including Debian LTS, to select the correct patched package.
Check Siemens SSA-265688 where Siemens products or appliances are in scope.
Review VFIO PCI passthrough use until affected hosts are patched.
Avoid changing interrupt handling manually without vendor guidance.
Validation and detection
Inventory Linux kernel versions across virtualization and passthrough hosts.
Identify hosts loading VFIO PCI or assigning PCI devices to guests.
Prioritize devices using legacy INTx or lacking DisINTx support.
Confirm the relevant stable patch is present in the running vendor kernel.
After update, regression-test affected passthrough devices and guest availability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27437 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.