Security readout for executives and security teams
Plain-English summary
CVE-2025-40073 is a Linux kernel crash bug in the Qualcomm MSM DRM display driver path. A null pointer dereference can occur during display plane validation, causing a kernel oops. Business impact is most likely local denial of service on affected systems using this driver, not confirmed data theft or remote compromise.
Executive priority
Address in normal kernel maintenance cycles, faster for shared, kiosk, embedded, or mobile-like devices where local users can reach display interfaces. Current evidence supports availability risk, not confirmed remote exploitation.
Technical view
The flaw is in drm/msm DPU plane handling. Current code validates SSPP sharing for a plane before that plane has an SSPP assigned, dereferencing NULL during multi-rect capability checks. The reported trace shows the issue triggered through DRM atomic plane update ioctl flow. Upstream stable commits skip SSPP validation when the current plane is not ready.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or commits with the Qualcomm MSM DRM/DPU display stack enabled. The CVE data lists Linux 6.16 through 6.17.3/6.18-related affected entries, but version metadata is not fully clear.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The trace shows local user-space interaction with DRM ioctls via modetest causing a kernel crash. Treat this as a local stability and availability concern unless vendor guidance states otherwise.
Researcher notes
The public record lacks CVSS, CWE, and detailed downstream affected distribution mapping. Analysis should focus on the drm/msm DPU atomic plane update path and whether the stable commits are present. Avoid assuming impact beyond NULL pointer kernel crash without further vendor evidence.
Mitigation direction
Review vendor kernel advisories for CVE-2025-40073 applicability.
Apply Linux stable updates containing the referenced drm/msm fix.
Prioritize affected Qualcomm MSM display devices with local user access.
Restrict unnecessary local access to DRM device nodes where operationally feasible.
Track downstream Android or device-vendor kernel updates if applicable.
Validation and detection
Inventory kernels and identify systems using the msm DRM driver.
Compare deployed kernel source or package changelog against referenced stable commits.
Confirm whether affected version ranges apply to your distribution kernel.
Check for recent kernel oops logs referencing dpu_plane_is_multirect_capable.
Validate remediation in a non-production display test environment.
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-2025-40073 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 28, 2025, 11:48 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.