| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37951: drm/v3d: Add job to pending list if the reset was skipped |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37951 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.1.139 with commit 5235b56b7e5449d990d21d78723b1a5e7bb5738e |
| Fixed in 6.6.91 with commit 12125f7d9c15e6d8ac91d10373b2db2f17dcf767 |
| Fixed in 6.12.29 with commit a5f162727b91e480656da1876247a91f651f76de |
| Fixed in 6.14.7 with commit 422a8b10ba42097a704d6909ada2956f880246f2 |
| Fixed in 6.15 with commit 35e4079bf1a2570abffce6ababa631afcf8ea0e5 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-37951 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/gpu/drm/v3d/v3d_sched.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| 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 |
