CVE-2026-64099
Last modified
CVE-2026-64099 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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 that triggers the use-after-free also leaks one syncobj reference per query. Unify the CPU job teardown into the CPU job's kref destructor, mirroring v3d_render_job_free(). The scheduler's .free_job slot reverts to the generic v3d_sched_job_free() and the fail label drops the manual kvfree() calls, leaving a single teardown path that is reached from both the scheduler and the ioctl error path. That removes the use-after-free, the NULL dereference, and the syncobj leak by construction.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64099?
How severe is CVE-2026-64099?
How do I fix CVE-2026-64099?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64093In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64094In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64095In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64096In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64097In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64098In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6410@fastify/static versions 8.0.0 through 9.1.0 allow path trav…5.3
- CVE-2026-64100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64101In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64102In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64103In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64104In the Linux kernel, the following vulnerability has been re…8.7
Are you affected by CVE-2026-64099?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
