CVE-2023-53123PCI: s390: Fix use-after-free of PCI resources with per-function hotplug
- 7.8HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: s390: Fix use-after-free of PCI resources with per-function hotplug On s390 PCI functions may be hotplugged individually even when they belong to a multi-function device. In particular on an SR-IOV device VFs may be removed and later re-added. In commit a50297cf8235 ("s390/pci: separate zbus creation from scanning") it was missed however that struct pci_bus and struct zpci_bus's resource list retained a reference to the PCI functions MMIO resources even though those resources are released and freed on hot-unplug. These stale resources may subsequently be claimed when the PCI function re-appears resulting in use-after-free. One idea of fixing this use-after-free in s390 specific code that was investigated was to simply keep resources around from the moment a PCI function first appeared until the whole virtual PCI bus created for a multi-function device disappears. The problem with this however is that due to the requirement of artificial MMIO addreesses (address cookies) extra logic is then needed to keep the address cookies compatible on re-plug. At the same time the MMIO resources semantically belong to the PCI function so tying their lifecycle to the function seems more logical. Instead a simpler approach is to remove the resources of an individually hot-unplugged PCI function from the PCI bus's resource list while keeping the resources of other PCI functions on the PCI bus untouched. This is done by introducing pci_bus_remove_resource() to remove an individual resource. Similarly the resource also needs to be removed from the struct zpci_bus's resource list. It turns out however, that there is really no need to add the MMIO resources to the struct zpci_bus's resource list at all and instead we can simply use the zpci_bar_struct's resource pointer directly.
Timeline
ID reserved
By Linux
Published
- 18 months later
· 18 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 – < 437bb839e36cc9f35adc6d2a2bf113b7a0fc9985
- affected a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 – < a2410d0c3d2d714ed968a135dfcbed6aa3ff7027
- affected a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 – < b99ebf4b62774e690e73a551cf5fbf6f219bdd96
- affected a50297cf8235b062bcdeaa8b1dad58e69d3e1b43 – < ab909509850b27fd39b8ba99e44cda39dbc3858c
- affected 5.13
- unaffected < 5.13
- unaffected 5.15.104 – ≤ 5.15.*
- unaffected 6.1.21 – ≤ 6.1.*
- unaffected 6.2.8 – ≤ 6.2.*
- unaffected 6.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/437bb839e36cc9f35adc6d2a2bf113b7a0fc9985 (opens in a new tab)
- https://git.kernel.org/stable/c/a2410d0c3d2d714ed968a135dfcbed6aa3ff7027 (opens in a new tab)
- https://git.kernel.org/stable/c/b99ebf4b62774e690e73a551cf5fbf6f219bdd96 (opens in a new tab)
- https://git.kernel.org/stable/c/ab909509850b27fd39b8ba99e44cda39dbc3858c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-13151 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53123)Record last updated .