Bug 2367571 (CVE-2025-37951) - CVE-2025-37951 kernel: drm/v3d: Add job to pending list if the reset was skipped
Summary: CVE-2025-37951 kernel: drm/v3d: Add job to pending list if the reset was skipped
Keywords:
Status: NEW
Alias: CVE-2025-37951
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-20 17:01 UTC by OSIDB Bzimport
Modified: 2025-05-21 07:05 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-20 17:01:25 UTC
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.

Comment 1 Avinash Hanwate 2025-05-21 06:57:36 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025052001-CVE-2025-37951-1e36@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.