LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42127: drm/lima: fix shared irq handling on driver remove

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the drm/lima driver’s shutdown path. During driver removal, interrupts could still fire after device clocks were disabled, causing a crash in specific debug/shared-interrupt conditions. The sources show a kernel fix, but no CVSS score or active exploitation evidence.

Executive priority

Treat as routine kernel maintenance unless the organization runs affected Linux graphics stacks where driver unload or debug configurations are operationally relevant. No source shows active exploitation or severe business impact.

Technical view

The lima DRM driver used devm-managed shared IRQs that remained registered late in removal. Interrupt handlers could access device registers after clocks were disabled. The fix unregisters interrupts during each lima device finishing callback before clocks are fully disabled.

Likely exposure

Exposure appears limited to Linux systems using affected kernel builds with the lima DRM driver present. The source specifically mentions crashes during driver removal with CONFIG_DEBUG_SHIRQ enabled, suggesting narrow operational impact rather than broad remote exposure.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation. The described trigger is a crash during driver removal in a debug shared-IRQ configuration; no remote attack path is evidenced.

Researcher notes

Evidence supports a local kernel crash condition in a specific driver teardown path. Missing data includes CVSS, CWE mapping, exploitability analysis, and precise distribution-by-distribution affected package status beyond the provided Debian LTS reference.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Apply relevant Debian LTS kernel updates where applicable.
  • Check distribution advisories for the fixed kernel version on deployed systems.
  • Avoid unnecessary lima driver removal on unpatched affected systems.

Validation and detection

  • Inventory Linux systems using kernels in the affected ranges.
  • Check whether the drm/lima driver is built, loaded, or packaged.
  • Confirm installed kernel includes the applicable stable fix commit.
  • Review vendor advisories for backported fixes rather than version numbers alone.
Prepared
Confidence
medium
Sources
10

Public sources used

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-42127 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa1d2a6339961efc078208dc3b2f006e9e9a8e119, a1d2a6339961efc078208dc3b2f006e9e9a8e119, a1d2a6339961efc078208dc3b2f006e9e9a8e119, a1d2a6339961efc078208dc3b2f006e9e9a8e119, a1d2a6339961efc078208dc3b2f006e9e9a8e119, a1d2a6339961efc078208dc3b2f006e9e9a8e119, a1d2a6339961efc078208dc3b2f006e9e9a8e119unaffected
LinuxLinux5.2, 0, 5.4.280, 5.10.222, 5.15.163, 6.1.98, 6.6.39, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.