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-26813vfio/platform: Create persistent IRQ handlers

Description

In the Linux kernel, the following vulnerability has been resolved: vfio/platform: Create persistent IRQ handlers The vfio-platform SET_IRQS ioctl currently allows loopback triggering of an interrupt before a signaling eventfd has been configured by the user, which thereby allows a NULL pointer dereference. Rather than register the IRQ relative to a valid trigger, register all IRQs in a disabled state in the device open path. This allows mask operations on the IRQ to nest within the overall enable state governed by a valid eventfd signal. This decouples @masked, protected by the @locked spinlock from @trigger, protected via the @igate mutex. In doing so, it's guaranteed that changes to @trigger cannot race the IRQ handlers because the IRQ handler is synchronously disabled before modifying the trigger, and loopback triggering of the IRQ via ioctl is safe due to serialization with trigger changes via igate. For compatibility, request_irq() failures are maintained to be local to the SET_IRQS ioctl rather than a fatal error in the open device path. This allows, for example, a userspace driver with polling mode support to continue to work regardless of moving the request_irq() call site. This necessarily blocks all SET_IRQS access to the failed index.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 2 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-26813, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.23% · top 86% of all CVEs (18 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 57f972e2b341dd6a73533f9293ec55d584a5d833 – < 07afdfd8a68f9eea8db0ddc4626c874f29d2ac5e
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < 09452c8fcbd7817c06e8e3212d99b45917e603a5
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < cc5838f19d39a5fef04c468199699d2a4578be3a
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < 7932db06c82c5b2f42a4d1a849d97dba9ce4a362
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < 62d4e43a569b67929eb3319780be5359694c8086
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < d6bedd6acc0bcb1e7e010bc046032e47f08d379f
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < 0f8d8f9c2173a541812dd750529f4a415117eb29
    • affected 57f972e2b341dd6a73533f9293ec55d584a5d833 – < 675daf435e9f8e5a5eab140a9864dfad6668b375
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • 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

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .