Menu

Star on GitHub · 3.2k

CVE-2026-64049

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…

Published Jul 19, 2026EPSS 0.16%

Overview

CVE-2026-64049 is a known-severity vulnerability. It was published on July 19, 2026.

Technical description

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/

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64049?

CVE-2026-64049 is a known-severity vulnerability. It was published on July 19, 2026.

How severe is CVE-2026-64049?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64049?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64049?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64049 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.