# s390/pci: Fix missing check for zpci_create_device() error return

CVE record · `CVE-2025-37974`

- **Identifiers:** `CVE-2025-37974`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 20 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 20 May 2025, 16:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `1f3b309108fd0660ea8614a72328ba866ccd3378 to before be54b750c333a9db7c3b3686846bb06b07b011fe` (git)
  - affected: `0467cdde8c4320bbfdb31a8cff1277b202f677fc to before 2769b718e164df983c20c314b263a71a699be6cd` (git)
  - affected: `0467cdde8c4320bbfdb31a8cff1277b202f677fc to before 42420c50c68f3e95e90de2479464f420602229fc` (git)
  - affected: `6.12.5 to before 6.12.29` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.13`
  - unaffected: `before 6.13` (semver)
  - unaffected: `6.12.29 to 6.12.*, inclusive` (semver)
  - unaffected: `6.14.7 to 6.14.*, inclusive` (semver)
  - unaffected: `6.15 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel s390 PCI code is affected in several version ranges, including 6.12.5 before 6.12.29 and 6.13. A missing check on an error return from zpci_create_device() can lead to an error pointer being dereferenced as a device structure. The source gives few details on how an attacker could trigger this. Upgrade to 6.12.29 or later in the 6.12 series, 6.14.7 or later in the 6.14 series, or 6.15 or later; no fixed version for 6.13 is listed.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 20 May 2025, 16:47 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-37974)
- 20 May 2025, 17:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-37974)

## Sources

- [CVE List: CVE-2025-37974](https://www.cve.org/CVERecord?id=CVE-2025-37974)
- [NVD: CVE-2025-37974](https://nvd.nist.gov/vuln/detail/CVE-2025-37974)

### References from the CNA

- <https://git.kernel.org/stable/c/be54b750c333a9db7c3b3686846bb06b07b011fe>
- <https://git.kernel.org/stable/c/2769b718e164df983c20c314b263a71a699be6cd>
- <https://git.kernel.org/stable/c/42420c50c68f3e95e90de2479464f420602229fc>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-37974>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-37974/>. Everything for agents: <https://agentprime.io/llms.txt>.
