CVE-2025-21697
drm/v3d: Ensure job pointer is set to NULL after job completion
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Ensure job pointer is set to NULL after job completion After a job completes, the corresponding pointer in the device must be set to NULL. Failing to do so triggers a warning when unloading the driver, as it appears the job is still active. To prevent this, assign the job pointer to NULL after completing the job, indicating the job has finished.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.19
References 7
git.kernel.org
- stable/c/1bd6303d08c85072ce40ac01a767ab67195105bd
- stable/c/a34050f70e7955a359874dff1a912a748724a140
- stable/c/14e0a874488e79086340ba8e2d238cb9596b68a8
- stable/c/2a1c88f7ca5c12dff6fa6787492ac910bb9e4407
- stable/c/63195bae1cbf78f1d392b1bc9ae4b03c82d0ebf3
- stable/c/b22467b1ae104073dcb11aa78562a331cd7fb0e0
- stable/c/e4b5ccd392b92300a2b341705cc4805681094e49