CVE-2026-64099drm/v3d: Fix use-after-free of CPU job query arrays on error path
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Aug 5, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 9ba0ff3e083f6a4a0b6698f06bfff74805fefa5f before acd55ea40d03e06f20a9986363019e0e5173990e; 9ba0ff3e083f6a4a0b6698f06bfff74805fefa5f builds before 0f8efc45740b0628a787d1b0be8a0ddabd700625; from 9ba0ff3e083f6a4a0b6698f06bfff74805fefa5f before 69c2a1fec2e7ca25598180816f3bc56e1842eb41; from 9ba0ff3e083f6a4a0b6698f06bfff74805fefa5f before b0fe80c0b9250b35e2211bf3117e7aca814a21b0 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.8 before 6.12.93; from 6.13 before 6.18.34; from 6.19 before 7.0.11; 7.1; 7.1; 7.1; 7.1 | NVD |
References
- https://git.kernel.org/stable/c/acd55ea40d03e06f20a9986363019e0e5173990epatch
- https://git.kernel.org/stable/c/0f8efc45740b0628a787d1b0be8a0ddabd700625patch
- https://git.kernel.org/stable/c/69c2a1fec2e7ca25598180816f3bc56e1842eb41patch
- https://git.kernel.org/stable/c/b0fe80c0b9250b35e2211bf3117e7aca814a21b0patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.