Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-27437vfio/pci: Disable auto-enable of exclusive INTx IRQ

Description

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

  1. ID reserved

    By Linux

  2. · 40 days later

    Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-27437, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 26389925d6c2126fb777821a0a983adca7ee6351
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 561d5e1998d58b54ce2bbbb3e843b669aa0b3db5
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < b7a2f0955ffceffadfe098b40b50307431f45438
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 139dfcc4d723ab13469881200c7d80f49d776060
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 2a4a666c45107206605b7b5bc20545f8aabc4fa2
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < 3b3491ad0f80d913e7d255941d4470f4a4d9bfda
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < bf0bc84a20e6109ab07d5dc072067bd01eb931ec
    • affected 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – < fe9a7082684eb059b925c535682e68c34d487d43
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 5.4.274 – ≤ 5.4.*
    • unaffected 5.10.215 – ≤ 5.10.*
    • unaffected 5.15.154 – ≤ 5.15.*
    • unaffected 6.1.84 – ≤ 6.1.*
    • unaffected 6.6.24 – ≤ 6.6.*
    • unaffected 6.7.12 – ≤ 6.7.*
    • unaffected 6.8.3 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-27437 badge
[![CVE-2024-27437](https://cveledger.app/badge/CVE-2024-27437.svg)](https://cveledger.app/cve/CVE-2024-27437)

Record last updated .