# PCI: s390: Fix use-after-free of PCI resources with per-function hotplug

CVE record · `CVE-2023-53123`

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

Published by the CVE Program (CNA: Linux) at 2 May 2025, 15:55 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: `a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 to before 437bb839e36cc9f35adc6d2a2bf113b7a0fc9985` (git)
  - affected: `a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 to before a2410d0c3d2d714ed968a135dfcbed6aa3ff7027` (git)
  - affected: `a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 to before b99ebf4b62774e690e73a551cf5fbf6f219bdd96` (git)
  - affected: `a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 to before ab909509850b27fd39b8ba99e44cda39dbc3858c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.13`
  - unaffected: `before 5.13` (semver)
  - unaffected: `5.15.104 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.21 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2.8 to 6.2.*, inclusive` (semver)
  - unaffected: `6.3 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's s390 PCI code is affected from version 5.13 until fixed. Hot-unplugging and re-adding an individual PCI function can leave stale MMIO resources in use, causing a use-after-free. The source gives few details on what an attacker needs. Upgrade to 5.15.104 or later, 6.1.21 or later, 6.2.8 or later, or 6.3 or later.

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 9th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

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

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/437bb839e36cc9f35adc6d2a2bf113b7a0fc9985>
- <https://git.kernel.org/stable/c/a2410d0c3d2d714ed968a135dfcbed6aa3ff7027>
- <https://git.kernel.org/stable/c/b99ebf4b62774e690e73a551cf5fbf6f219bdd96>
- <https://git.kernel.org/stable/c/ab909509850b27fd39b8ba99e44cda39dbc3858c>

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-2023-53123>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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