CVE-2025-38240: drm/mediatek: dp: drm_err => dev_err in HPD path to avoid NULL ptr
In the Linux kernel, the following vulnerability has been resolved:
drm/mediatek: dp: drm_err => dev_err in HPD path to avoid NULL ptr
The function mtk_dp_wait_hpd_asserted() may be called before the
`mtk_dp->drm_dev` pointer is assigned in mtk_dp_bridge_attach().
Specifically it can be called via this callpath:
- mtk_edp_wait_hpd_asserted
- [panel probe]
- dp_aux_ep_probe
Using "drm" level prints anywhere in this callpath causes a NULL
pointer dereference. Change the error message directly in
mtk_dp_wait_hpd_asserted() to dev_err() to avoid this. Also change the
error messages in mtk_dp_parse_capabilities(), which is called by
mtk_dp_wait_hpd_asserted().
While touching these prints, also add the error code to them to make
future debugging easier.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel stability flaw in the MediaTek DisplayPort/eDP driver. During hardware or panel probing, an error logging path can dereference a NULL pointer and crash the kernel. The source does not show remote exploitation, privilege escalation, or active exploitation.
Executive priority
Treat as targeted operational risk for MediaTek-based Linux display devices, not broad enterprise emergency evidence. Patch through normal kernel maintenance unless affected products are business-critical or crash-prone.
Technical view
mtk_dp_wait_hpd_asserted() can run before mtk_dp->drm_dev is assigned in mtk_dp_bridge_attach(). DRM-level error logging in that HPD-related call path can dereference the unset pointer. The fix changes affected messages to dev_err() and adds error codes for debugging.
Likely exposure
Exposure appears limited to Linux systems using the MediaTek DRM DisplayPort/eDP driver and the affected HPD or panel probe path. General Linux servers without this hardware path are unlikely to be exposed based on the provided evidence.
Exploitation context
CISA KEV status is false in the provided bundle. The sources describe a NULL pointer dereference during driver probing, not a weaponized attack path. No public exploit, attacker prerequisites, or remote trigger evidence is provided.
Researcher notes
The affected-version data is incomplete and commit-oriented. The primary root cause is pre-initialization use of drm_dev by logging in the HPD path. Avoid inferring exploitability beyond denial-of-service-style kernel crash risk without vendor or upstream analysis.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check Linux distribution advisories for CVE-2025-38240 package status.
Prioritize MediaTek-based devices using DisplayPort or embedded DisplayPort.
If updating is delayed, assess whether affected display functionality can be avoided.
Validation and detection
Inventory Linux kernels and MediaTek DRM DisplayPort/eDP usage.
Confirm whether the kernel package includes the referenced stable commit.
Review vendor advisories for affected and fixed release mapping.
Test representative MediaTek DP/eDP hardware after updating.
Monitor kernel logs for HPD or panel probe NULL dereference crashes.
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-38240 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
6Source 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.
Apr 18, 2025, 07:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.