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-26814vfio/fsl-mc: Block calling interrupt handler without trigger

Description

In the Linux kernel, the following vulnerability has been resolved: vfio/fsl-mc: Block calling interrupt handler without trigger The eventfd_ctx trigger pointer of the vfio_fsl_mc_irq object is initially NULL and may become NULL if the user sets the trigger eventfd to -1. The interrupt handler itself is guaranteed that trigger is always valid between request_irq() and free_irq(), but the loopback testing mechanisms to invoke the handler function need to test the trigger. The triggering and setting ioctl paths both make use of igate and are therefore mutually exclusive. The vfio-fsl-mc driver does not make use of irqfds, nor does it support any sort of masking operations, therefore unlike vfio-pci and vfio-platform, the flow can remain essentially unchanged.

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-26814, 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.22% · top 87% 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 cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < a563fc18583ca4f42e2fdd0c70c7c618288e7ede
    • affected cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < 250219c6a556f8c69c5910fca05a59037e24147d
    • affected cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < 083e750c9f5f4c3bf61161330fb84d7c8e8bb417
    • affected cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < ee0bd4ad780dfbb60355b99f25063357ab488267
    • affected cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < de87511fb0404d23b6da5f4660383b6ed095e28d
    • affected cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < 6ec0d88166dac43f29e96801c0927d514f17add9
    • affected cc0ee20bd96971c10eba9a83ecf1c0733078a083 – < 7447d911af699a15f8d050dfcb7c680a86f87012
  • Linux · Linux

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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .