CVE-2025-21697: drm/v3d: Ensure job pointer is set to NULL after job completion
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.
Security readout for executives and security teams
Plain-English summary
A Linux V3D graphics-driver bookkeeping error leaves a completed job appearing active. The supplied description confirms a warning during driver unload, while the CVSS record rates potential confidentiality, integrity, and availability impact as high. Treat it as a locally reachable kernel issue, but note that the provided evidence does not explain how the warning becomes broader compromise.
Executive priority
Use high-priority, risk-based patching for affected V3D-enabled systems, especially shared or multi-user hosts. This is not evidenced as remotely exploitable or actively exploited, so emergency organization-wide action is unsupported. Require asset owners to confirm driver use, obtain distribution-specific fixed versions, and report exceptions where maintained updates are unavailable.
Technical view
After a V3D job completes, its device job pointer is not cleared to NULL. Stale state triggers a warning when the driver unloads. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, unchanged scope, and high CIA impacts. The source bundle provides stable-kernel fix commits but no demonstrated attack mechanism.
Likely exposure
Exposure is limited to Linux systems using the drm/v3d driver, with greater concern where untrusted users have local access. The bundle lists 4.19, 5.4.290, 5.10.234, 5.15.177, 6.1.127, 6.6.74, 6.12.11, and 6.13 as affected, but does not clearly define version-range boundaries. Confirm status through the distribution vendor.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation or a public exploit. The CVSS vector requires a local, low-privileged attacker and no user interaction. Evidence provided describes a stale pointer and unload warning, not a proven exploitation path, so real-world exploitability remains unclear.
Researcher notes
The supplied narrative establishes failure to clear a completed-job pointer and a resulting unload warning. It does not substantiate memory corruption, privilege escalation, or the high CIA consequences encoded by CVSS. Affected-version data is also ambiguous and includes repeated commit identifiers. Review referenced patches and distribution advisories before drawing conclusions about reachability or root cause beyond stale device state.
Mitigation direction
Obtain and install a vendor-supported kernel update containing the applicable stable fix.
Prioritize systems loading drm/v3d that also permit local access by untrusted users.
Consult distribution guidance to determine the first fixed package for each maintained kernel branch.
Reboot where required so the corrected kernel replaces the vulnerable running kernel.
Validation and detection
Identify systems loading drm/v3d and record their running kernel and package versions.
Compare each installed package with the distribution's CVE advisory and fixed-version guidance.
Confirm the updated kernel incorporates the applicable referenced Linux stable commit.
After reboot, verify the corrected kernel is active and review logs for V3D unload warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21697 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.