| 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-37987: pds_core: Prevent possible adminq overflow/stuck condition |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| pds_core: Prevent possible adminq overflow/stuck condition |
| |
| The pds_core's adminq is protected by the adminq_lock, which prevents |
| more than 1 command to be posted onto it at any one time. This makes it |
| so the client drivers cannot simultaneously post adminq commands. |
| However, the completions happen in a different context, which means |
| multiple adminq commands can be posted sequentially and all waiting |
| on completion. |
| |
| On the FW side, the backing adminq request queue is only 16 entries |
| long and the retry mechanism and/or overflow/stuck prevention is |
| lacking. This can cause the adminq to get stuck, so commands are no |
| longer processed and completions are no longer sent by the FW. |
| |
| As an initial fix, prevent more than 16 outstanding adminq commands so |
| there's no way to cause the adminq from getting stuck. This works |
| because the backing adminq request queue will never have more than 16 |
| pending adminq commands, so it will never overflow. This is done by |
| reducing the adminq depth to 16. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37987 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.4 with commit 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and fixed in 6.6.93 with commit 517f928cc0c133472618cbba18382b46f5f71ba3 |
| Issue introduced in 6.4 with commit 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and fixed in 6.12.26 with commit 2982e07ad72b48eb12c29a87a3f2126ea552688c |
| Issue introduced in 6.4 with commit 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and fixed in 6.14.5 with commit 5e3dc65675faad846420d24762e4faadc12d9392 |
| Issue introduced in 6.4 with commit 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and fixed in 6.15 with commit d9e2f070d8af60f2c8c02b2ddf0a9e90b4e9220c |
| |
| 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-37987 |
| 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/net/ethernet/amd/pds_core/core.c |
| drivers/net/ethernet/amd/pds_core/core.h |
| |
| |
| 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/517f928cc0c133472618cbba18382b46f5f71ba3 |
| https://git.kernel.org/stable/c/2982e07ad72b48eb12c29a87a3f2126ea552688c |
| https://git.kernel.org/stable/c/5e3dc65675faad846420d24762e4faadc12d9392 |
| https://git.kernel.org/stable/c/d9e2f070d8af60f2c8c02b2ddf0a9e90b4e9220c |
