# CVE-2025-37887: pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result

> A local attacker can cause a kernel crash or print garbage by triggering an uninitialized memory access in the pds_core driver via devlink commands.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-37887, DEBIAN-CVE-2025-37887, GHSA-mcq3-239h-fc92, ROOT-OS-UBUNTU-2404-CVE-2025-37887, UBUNTU-CVE-2025-37887

## What is CVE-2025-37887?

CVE-2025-37887 is a high-severity vulnerability in Linux kernel, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

pds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result

If the FW doesn't support the PDS_CORE_CMD_FW_CONTROL command
the driver might at the least print garbage and at the worst
crash when the user runs the "devlink dev info" devlink command.

This happens because the stack variable fw_list is not 0
initialized which results in fw_list.num_fw_slots being a
garbage value from the stack.  Then the driver tries to access
fw_list.fw_names[i] with i >= ARRAY_SIZE and runs off the end
of the array.

Fix this by initializing the fw_list and by not failing
completely if the devcmd fails because other useful information
is printed via devlink dev info even if the devcmd fails.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2025-37887?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-37887?

Apply the vendor's patch.

## Is CVE-2025-37887 being exploited?

There is no known exploitation of CVE-2025-37887 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37887 and fix it if it is affected.

What it is: CVE-2025-37887 is a high-severity vulnerability in Linux kernel, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37887 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-37887/ (Markdown: https://insights.sbomify.com/CVE-2025-37887/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-37887
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-37887
- OSV: https://osv.dev/vulnerability/CVE-2025-37887

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-37887/
Summaries are generated and may contain mistakes; the official description above is the record.