CVE-2025-37987 Details
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.
A vulnerability in the Linux kernel's pds_core component can lead to an admin queue (adminq) overflow and a stuck condition, preventing commands from being processed. The adminq is managed by a lock that allows only one command to be posted at a time, but completions occur in a different context. This discrepancy can result in multiple adminq commands being posted sequentially, all waiting for completion. The adminq request queue on the firmware side is only 16 entries long and lacks proper overflow or stuck condition prevention. As a result, the adminq can become stuck, halting command processing and completion notifications from the firmware. The vulnerability has been addressed by limiting the number of outstanding adminq commands to 16, ensuring the adminq does not get stuck or overflow.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2982e07ad72b48eb12c29a87a3f2126ea552688c | kernel.org | Patch |
| https://git.kernel.org/stable/c/517f928cc0c133472618cbba18382b46f5f71ba3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5e3dc65675faad846420d24762e4faadc12d9392 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d9e2f070d8af60f2c8c02b2ddf0a9e90b4e9220c | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.4, < 6.6.93 >= 6.7, < 6.12.26 >= 6.13, < 6.14.5 6.15 rc1 6.15 rc2 6.15 rc3 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 14, 2025 | Initial Analysis | [email protected] |
| Jun 4, 2025 | CVE Modified | kernel.org |
| May 20, 2025 | New CVE Received | kernel.org |