CVE-2025-37951: drm/v3d: Add job to pending list if the reset was skipped

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-05-20 · updated 2026-06-17
Weakness: CWE-401

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.

Affected products

Debian Linux: 11.0
Linux kernel: from 4.18 before 6.1.139; from 6.2 before 6.6.91; from 6.7 before 6.12.29; from 6.13 before 6.14.7; 6.15-rc1, 6.15-rc2, 6.15-rc3, 6.15-rc4, 6.15-rc5 — fixed in 6.1.139, 6.12.29, 6.14.7, 6.6.91

How to fix

Upgrade to a fixed version: Linux kernel 6.1.139, 6.12.29, 6.14.7, 6.6.91. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-37951 or the next vulnerability affects your stack