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-42127drm/lima: fix shared irq handling on driver remove

Description

In the Linux kernel, the following vulnerability has been resolved: drm/lima: fix shared irq handling on driver remove lima uses a shared interrupt, so the interrupt handlers must be prepared to be called at any time. At driver removal time, the clocks are disabled early and the interrupts stay registered until the very end of the remove process due to the devm usage. This is potentially a bug as the interrupts access device registers which assumes clocks are enabled. A crash can be triggered by removing the driver in a kernel with CONFIG_DEBUG_SHIRQ enabled. This patch frees the interrupts at each lima device finishing callback so that the handlers are already unregistered by the time we fully disable clocks.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 22 months 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-42127, 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 (19 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 a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < 0d60c43df59ef01c08dc7b0c45495178f9d05a13
    • affected a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < 25d0d9b83d855cbc5d5aa5ae3cd79d55ea0c84a8
    • affected a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < 17fe8b75aaf0bb1bdc31368963446b421c22d0af
    • affected a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < 0a487e977cb8897ae4c51ecd34bbaa2b005266c9
    • affected a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < 04d531b9a1875846d4f89953b469ad463aa7a770
    • affected a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < b5daf9217a50636a969bc1965f827878aeb09ffe
    • affected a1d2a6339961efc078208dc3b2f006e9e9a8e119 – < a6683c690bbfd1f371510cb051e8fa49507f3f5e
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.4.280 – ≤ 5.4.*
    • unaffected 5.10.222 – ≤ 5.10.*
    • unaffected 5.15.163 – ≤ 5.15.*
    • unaffected 6.1.98 – ≤ 6.1.*
    • unaffected 6.6.39 – ≤ 6.6.*
    • unaffected 6.9.9 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .