CVE-2025-21697: drm/v3d: Ensure job pointer is set to NULL after job completion

Published Feb 12, 2025
·
Updated

drm/v3d: Ensure job pointer is set to NULL after job completion

Affected Software

20 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.19<5.4.290
Linux Linux kernel>=5.5<5.10.234
Linux Linux kernel>=5.11<5.15.177
Linux Linux kernel>=5.16<6.1.127
Linux Linux kernel>=6.2<6.6.74
Linux Linux kernel>=6.7<6.12.11
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
Linux Linux kernel=6.13-rc3
Linux Linux kernel=6.13-rc4
Linux Linux kernel=6.13-rc5
Linux Linux kernel=6.13-rc6
Linux Linux kernel=6.13-rc7
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.176.3-3<5.15.180.1-1
5.15.180.1-1
Microsoft azl3 kernel 6.6.64.2-9<6.6.76.1-1
6.6.76.1-1
Microsoft azl3 kernel 6.6.76.1-1<6.6.76.1-1
6.6.76.1-1
Microsoft cbl2 kernel 5.15.180.1-1<5.15.180.1-1
5.15.180.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.15.180.1-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.76.1-1
  5. Configuration

    Set the corresponding drm/v3d device job pointer to NULL immediately after the job completes, so the driver no longer appears to have an active job when unloading (prevents warnings on unload).

    Linux kernel (drm/v3d) job pointer = NULL

Event History

Feb 12, 2025
CVE Published
via MITRE·01:27 PM
Data Sourced
via MITRE·01:27 PM
DescriptionSeverity
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityAffected Software
Mar 14, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
Updated
via Microsoft·07:00 AM
DescriptionSeverity
May 2, 2025
Data Sourced
via Ubuntu·11:49 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-21697?

CVE-2025-21697 has a medium severity rating due to the potential for driver unloading warnings that may affect system stability.

2

How do I fix CVE-2025-21697?

To fix CVE-2025-21697, ensure that you update to the latest version of the Linux kernel where this vulnerability is addressed.

3

What is the impact of CVE-2025-21697?

The impact of CVE-2025-21697 primarily affects the ability to unload the driver cleanly, potentially causing system instability.

4

Which systems are affected by CVE-2025-21697?

CVE-2025-21697 affects systems running specific versions of the Linux kernel with the DRM V3D component.

5

Is CVE-2025-21697 being actively exploited?

As of now, there are no public reports of CVE-2025-21697 being actively exploited in the wild.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203