VulnerabilityPublished 20 May 2025Updated 14 Nov 2025

CVE-2025-37987: Linux kernel · pds_core: Prevent possible adminq overflow/stuck condition

Source GCVE Database

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 13 Nov 2026, 18:51 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-pvfr-278h-v324

What to do

AI-suggested

A fix is available that reduces the adminq depth to 16, preventing more than 16 outstanding adminq commands and thereby avoiding overflow and stuck conditions. Users should apply the official kernel updates that include this fix. No additional mitigation steps are indicated.

Description

CVE-2025-37987 addresses a vulnerability in the Linux kernel's pds_core component where the adminq (administration queue) could become stuck or overflow. The issue arises because the adminq request queue on the firmware side is limited to 16 entries and lacks adequate retry or overflow prevention mechanisms. The vulnerability could cause the adminq to stop processing commands, leading to a denial of service condition. The fix involves limiting the number of outstanding adminq commands to 16, preventing overflow and stuck conditions.

Impact

This vulnerability can cause the adminq to become stuck, resulting in commands no longer being processed and completions not being sent by the firmware. This leads to a denial of service (DoS) condition affecting system availability. The CVSS score of 5.5 (medium severity) reflects the local attack vector, low complexity, low privileges required, no user interaction, and impact limited to availability.

Summary

The Linux kernel's pds_core adminq is protected by a lock that prevents multiple simultaneous command postings, but completions occur asynchronously, allowing multiple commands to be queued sequentially. The firmware's backing adminq request queue has a fixed size of 16 entries and lacks retry or overflow prevention, which can cause the queue to become stuck and stop processing commands. The vulnerability is mitigated by reducing the adminq depth to 16, ensuring no more than 16 outstanding commands exist at any time, thereby preventing overflow and stuck conditions.

References

Community reviews

Loading reviews…