CVE-2025-37951

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

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

References

• https://git.kernel.org/stable/c/5235b56b7e5449d990d21d78723b1a5e7bb5738e ↗
• https://git.kernel.org/stable/c/12125f7d9c15e6d8ac91d10373b2db2f17dcf767 ↗
• https://git.kernel.org/stable/c/a5f162727b91e480656da1876247a91f651f76de ↗
• https://git.kernel.org/stable/c/422a8b10ba42097a704d6909ada2956f880246f2 ↗
• https://git.kernel.org/stable/c/35e4079bf1a2570abffce6ababa631afcf8ea0e5 ↗
• https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html ↗