Menu

Star on GitHub · 3.2k

CVE-2026-64099

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Fix use-after-free of CPU job query arrays on error path The CPU job ioctl's fail label calls kvfree() on cpu_job's ti…

Published Jul 19, 2026CWE-416EPSS 0.13%

Overview

CVE-2026-64099 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

drm/v3d: Fix use-after-free of CPU job query arrays on error path

The CPU job ioctl's fail label calls kvfree() on cpu_job's timestamp and

performance query arrays after v3d_job_cleanup(), which drops the job's

last reference and frees cpu_job. Reading cpu_job at that point is a

use-after-free. Also, on the early v3d_job_init() failure path, it is a

NULL dereference, since v3d_job_deallocate() zeroes the local pointer.

In the success path, the arrays are released from the scheduler's

.free_job callback, but on the error path, they are freed manually, as

the job was never pushed to the scheduler. While the success path deals

with this correctly, the fail path doesn't.

On top of that, the manual kvfree() calls only free the array storage;

they don't drm_syncobj_put() the per-query syncobjs that

v3d_timestamp_query_info_free() and v3d_performance_query_info_free()

release on the success path. So the same fail path tha

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-64099?

CVE-2026-64099 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64099?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

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-64099?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64099 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.

Related HIGH CVEs from 2026

View all