LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38622: drm/msm/dpu: Add callback function pointer check before its call

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: Add callback function pointer check before its call In dpu_core_irq_callback_handler() callback function pointer is compared to NULL, but then callback function is unconditionally called by this pointer. Fix this bug by adding conditional return. Found by Linux Verification Center (linuxtesting.org) with SVACE. Patchwork: https://patchwork.freedesktop.org/patch/588237/

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel display-driver bug where code could call a missing callback after detecting it was null. The provided sources do not state business impact, exploitation path, or attacker requirements. Treat it as a kernel maintenance exposure, especially on systems using the affected DRM MSM DPU driver.

Executive priority

Track and patch through normal kernel update cycles unless asset inventory shows critical systems using the affected driver. The available evidence does not support emergency response claims, but kernel bugs still merit timely remediation because impact details are incomplete.

Technical view

The flaw is in dpu_core_irq_callback_handler() in drm/msm/dpu. The handler checked a callback pointer for NULL, then still called it unconditionally. The fix adds a conditional return before the call. Sources list affected Linux kernel versions and stable kernel commits, but no CVSS, CWE, or exploit details.

Likely exposure

Exposure appears limited to Linux kernels with the affected drm/msm/dpu code path present and relevant. Systems not using that driver are likely less exposed, but the source bundle does not provide build, configuration, or distribution-specific package details.

Exploitation context

The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. The record says the issue was found by Linux Verification Center using SVACE. Attacker control, required privileges, and practical exploitability are not described.

Researcher notes

The key fact is a null function pointer check followed by unconditional invocation in the DPU IRQ callback handler. Sources do not provide a reproducer, crash trace, CVSS vector, affected configurations, or exploit preconditions. Validate against exact downstream kernel patches rather than upstream version strings alone.

Mitigation direction

  • Apply a Linux kernel update or vendor backport containing the referenced stable fixes.
  • Check distribution advisories for the fixed package version covering CVE-2024-38622.
  • Prioritize assets running affected kernels with drm/msm/dpu enabled or loaded.
  • Avoid unofficial workarounds unless confirmed by the kernel or distribution vendor.

Validation and detection

  • Inventory Linux systems running affected kernel versions listed in the CVE source bundle.
  • Check whether the deployed kernel includes one of the referenced stable fix commits or a vendor backport.
  • Confirm whether drm/msm/dpu is built, enabled, or loaded on relevant assets.
  • Retest normal display and suspend/resume behavior after kernel updates.
Prepared
Confidence
medium
Sources
5

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-38622 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
4Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc929ac60b3ed34accd25a052a4833e418900f466, c929ac60b3ed34accd25a052a4833e418900f466, c929ac60b3ed34accd25a052a4833e418900f466unaffected
LinuxLinux5.19, 0, 6.6.33, 6.9.4, 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.