CVE-2026-64049: drm/msm/adreno: fix userspace-triggered crash on a2xx-a4xx
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/adreno: fix userspace-triggered crash on a2xx-a4xx
Before a5xx Adreno driver will not try fetching UBWC params (because
those generations didn't support UBWC anyway), however it's still
possible to query UBWC-related params from the userspace, triggering
possible NULL pointer dereference. Check for UBWC config in
adreno_get_param() and return sane defaults if there is none.
Patchwork: https://patchwork.freedesktop.org/patch/717778/
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel graphics driver flaw where local userspace can trigger a crash on systems using older Qualcomm Adreno GPU generations. The source describes a NULL pointer dereference, so the clearest business impact is local availability disruption, not confirmed data theft or remote compromise.
Executive priority
Treat this as a targeted availability risk until vendor severity is published. It is most urgent for fleets where untrusted local users or apps can interact with affected Adreno graphics devices.
Technical view
The drm/msm/adreno driver could fetch UBWC-related parameters even when pre-a5xx Adreno generations lack UBWC configuration. A userspace parameter query could therefore hit a NULL pointer dereference. The fix checks for missing UBWC config in adreno_get_param() and returns sane defaults.
Likely exposure
Exposure appears limited to Linux systems using the msm Adreno DRM driver with a2xx-a4xx class hardware or affected kernel builds. The affected version data in the source is sparse and should be verified against distribution kernel advisories.
Exploitation context
The source says the crash is userspace-triggered, implying local access is relevant. There is no KEV listing and no cited evidence of active exploitation, public exploit use, remote reachability, or privilege escalation.
Researcher notes
The source supports a userspace-triggered NULL pointer dereference in Linux drm/msm/adreno. It does not establish remote attack surface, exploit maturity, impact beyond crash, or complete affected version mapping. Validate using kernel and distro commit lineage.
Mitigation direction
Apply kernel updates containing the referenced stable fixes when available.
Check Linux distribution advisories for backported fixes and affected package versions.
Prioritize shared, kiosk, mobile, embedded, or multi-user systems with Adreno GPUs.
Restrict untrusted local users where kernel updates are not yet available.
Validation and detection
Inventory Linux systems using the msm Adreno DRM driver.
Map installed kernel versions to distribution advisories and stable fix commits.
Review crash logs for NULL dereferences in drm/msm/adreno paths.
Confirm patched kernels include the UBWC config check in adreno_get_param().
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-2026-64049 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
4Source 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.
Jul 19, 2026, 15:39 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.