LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26667: drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup The commit 8b45a26f2ba9 ("drm/msm/dpu: reserve cdm blocks for writeback in case of YUV output") introduced a smatch warning about another conditional block in dpu_encoder_helper_phys_cleanup() which had assumed hw_pp will always be valid which may not necessarily be true. Lets fix the other conditional block by making sure hw_pp is valid before dereferencing it. Patchwork: https://patchwork.freedesktop.org/patch/574878/

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 bug in Qualcomm MSM display cleanup code. The code could dereference a display hardware pointer without first proving it was valid. The public record does not provide CVSS, a CWE, confirmed impact, or active exploitation evidence.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency based on available evidence. Prioritize affected device fleets or embedded platforms using Qualcomm MSM display drivers, then fold fixes into normal kernel patch cycles.

Technical view

CVE-2024-26667 was resolved by adding a validity check for hw_pp in dpu_encoder_helper_phys_cleanup() before dereference. The issue followed earlier DRM/MSM/DPU writeback-related changes and was identified as a Smatch warning. Fixes are referenced through Linux stable commits.

Likely exposure

Exposure appears limited to Linux kernels containing the DRM MSM DPU display code path, especially Qualcomm MSM display environments. The bundle lists Linux as affected and provides version markers, but it does not give a clean affected-version range.

Exploitation context

The source bundle does not report exploitation in the wild, and KEV is false. No public source in the bundle describes a working exploit, privilege requirement, or practical attack path.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability narrative, or direct impact statement is provided. Analysis should stay close to the patch: a missing hw_pp validity check before dereference in DRM/MSM/DPU cleanup logic.

Mitigation direction

  • Review vendor or distribution kernel advisories for CVE-2024-26667 applicability.
  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Prioritize systems using Qualcomm MSM DRM/DPU display functionality.
  • If patch timing is unclear, seek vendor guidance before changing driver configuration.

Validation and detection

  • Inventory Linux kernel versions and compare against vendor fixed builds.
  • Check whether DRM MSM DPU support is enabled or present in deployed kernels.
  • Review kernel package changelogs for the referenced stable commit IDs.
  • Confirm no production policy depends on unsupported direct wrangler-style kernel source assumptions.
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-26667 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxae4d721ce10057a4aa9f0d253e0d460518a9ef75, ae4d721ce10057a4aa9f0d253e0d460518a9ef75, ae4d721ce10057a4aa9f0d253e0d460518a9ef75, ae4d721ce10057a4aa9f0d253e0d460518a9ef75unaffected
LinuxLinux5.19, 0, 6.1.78, 6.6.17, 6.7.5, 6.8affected
Weakness

CWE details

No CWE listed

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