LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38390: drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails

In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails Calling a6xx_destroy() before adreno_gpu_init() leads to a null pointer dereference on: msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL); as gpu->pdev is only assigned in: a6xx_gpu_init() |_ adreno_gpu_init |_ msm_gpu_init() Instead of relying on handwavy null checks down the cleanup chain, explicitly de-allocate the LLC data and free a6xx_gpu instead. Patchwork: https://patchwork.freedesktop.org/patch/588919/

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38390 is a Linux kernel bug in the Qualcomm Adreno a6xx graphics driver path. When speedbin setup fails, cleanup can dereference a null pointer and crash kernel code. The public source does not provide CVSS, business impact detail, or exploitation evidence.

Executive priority

Treat as a targeted kernel stability risk, not an internet-wide emergency from the available evidence. Patch through normal kernel maintenance, with higher priority for fleets using Qualcomm Adreno a6xx graphics support.

Technical view

The issue is in drm/msm/a6xx cleanup ordering. Calling a6xx_destroy() before adreno_gpu_init() means gpu->pdev may not be initialized, yet msm_gpu_cleanup() uses it. Kernel stable fixes avoid that path by directly freeing LLC data and a6xx_gpu.

Likely exposure

Exposure appears limited to Linux kernels using the drm/msm/a6xx driver code path. Systems without this GPU driver path are unlikely exposed based on the provided sources. Exact distribution package status is not provided.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The source describes a null pointer dereference during a driver initialization failure path, but does not document attacker prerequisites or a public exploit.

Researcher notes

Evidence is limited to the CVE record and kernel stable references. No CVSS, CWE, exploitability analysis, or distribution-specific fix matrix is provided. Validate exposure against actual kernel configuration and vendor backport metadata.

Mitigation direction

  • Check vendor kernel advisories for CVE-2024-38390.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems using drm/msm/a6xx GPU support.
  • Track distribution backports rather than relying only on upstream version labels.

Validation and detection

  • Inventory running kernel versions on potentially affected systems.
  • Confirm whether drm/msm/a6xx support is present or enabled.
  • Verify vendor packages include the referenced stable commits.
  • Review crash logs for related a6xx initialization failures.
Prepared
Confidence
medium
Sources
6

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-38390 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
5Source 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
LinuxLinux76efc2453d0e8e5d6692ef69981b183ad674edea, 76efc2453d0e8e5d6692ef69981b183ad674edea, 76efc2453d0e8e5d6692ef69981b183ad674edea, 76efc2453d0e8e5d6692ef69981b183ad674edea, 5fea4202b5faccfc6449381a299e8ce4b994d666unaffected
LinuxLinux6.1, 0, 6.1.93, 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.