CVE-2025-39958iommu/s390: Make attach succeed when the device was surprise removed
- 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: iommu/s390: Make attach succeed when the device was surprise removed When a PCI device is removed with surprise hotplug, there may still be attempts to attach the device to the default domain as part of tear down via (__iommu_release_dma_ownership()), or because the removal happens during probe (__iommu_probe_device()). In both cases zpci_register_ioat() fails with a cc value indicating that the device handle is invalid. This is because the device is no longer part of the instance as far as the hypervisor is concerned. Currently this leads to an error return and s390_iommu_attach_device() fails. This triggers the WARN_ON() in __iommu_group_set_domain_nofail() because attaching to the default domain must never fail. With the device fenced by the hypervisor no DMAs to or from memory are possible and the IOMMU translations have no effect. Proceed as if the registration was successful and let the hotplug event handling clean up the device. This is similar to how devices in the error state are handled since commit 59bbf596791b ("iommu/s390: Make attach succeed even if the device is in error state") except that for removal the domain will not be registered later. This approach was also previously discussed at the link. Handle both cases, error state and removal, in a helper which checks if the error needs to be propagated or ignored. Avoid magic number condition codes by using the pre-existing, but never used, defines for PCI load/store condition codes and rename them to reflect that they apply to all PCI instructions.
Timeline
ID reserved
By Linux
- 6 months later
· 6 months later
Published
- 13 months later
· 13 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 · Modified | 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 (18 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 59bbf596791b89c7f88fdcac29dfc39c1221d25d – < 3b32cf6e279597d1b6477fb89d46abf65263c139
- affected 59bbf596791b89c7f88fdcac29dfc39c1221d25d – < 79fa3a19aa6114189b33e2ba1f393b0f635d7544
- affected 59bbf596791b89c7f88fdcac29dfc39c1221d25d – < 359613f2fa009587154511e4842e8ab9532edd15
- affected 59bbf596791b89c7f88fdcac29dfc39c1221d25d – < 9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.16.9 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References4
- https://git.kernel.org/stable/c/3b32cf6e279597d1b6477fb89d46abf65263c139 (opens in a new tab)
- https://git.kernel.org/stable/c/79fa3a19aa6114189b33e2ba1f393b0f635d7544 (opens in a new tab)
- https://git.kernel.org/stable/c/359613f2fa009587154511e4842e8ab9532edd15 (opens in a new tab)
- https://git.kernel.org/stable/c/9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73 (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-33325 (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-2025-39958)Record last updated .