CVE-2025-37951
Last modified
CVE-2025-37951 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Add job to pending list if the reset was skipped When a CL/CSD job times out, we check if the GPU has made any progress since the last timeout. If so, instead of resetting the hardware, we skip the reset and let the timer get rearmed. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Add job to pending list if the reset was skipped When a CL/CSD job times out, we check if the GPU has made any progress since the last timeout. If so, instead of resetting the hardware, we skip the reset and let the timer get rearmed. This gives long-running jobs a chance to complete. However, when `timedout_job()` is called, the job in question is removed from the pending list, which means it won't be automatically freed through `free_job()`. Consequently, when we skip the reset and keep the job running, the job won't be freed when it finally completes. This situation leads to a memory leak, as exposed in [1] and [2]. Similarly to commit 704d3d60fec4 ("drm/etnaviv: don't block scheduler when GPU is still active"), this patch ensures the job is put back on the pending list when extending the timeout.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.18, < 6.1.139 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.91 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.29 | — |
| Linux | Linux Kernel | >= 6.13, < 6.14.7 | — |
| Linux | Linux Kernel | 6.15 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-37951?
How severe is CVE-2025-37951?
How do I fix CVE-2025-37951?
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 2025
- CVE-2025-37946In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37947In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37948In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37949In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3795A vulnerability was found in DaiCuo 1.3.13. It has been rate…3.4
- CVE-2025-37950In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37952In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37953In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37954In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37955In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37956In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37957In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-37951?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
