Answer in brief
CVE-2025-39958 records a Unknown severity vulnerability in iommu/s390: Make attach succeed when the device was surprise removed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=59bbf596791b89c7f88fdcac29dfc39c1221d25d <3b32cf6e279597d1b6477fb89d46abf65263c139 || >=59bbf596791b89c7f88fdcac29dfc39c1221d25d <79fa3a19aa6114189b33e2ba1f393b0f635d7544 || >=59bbf596791b89c7f88fdcac29dfc39c1221d25d <359613f2fa009587154511e4842e8ab9532edd15 || >=59bbf596791b89c7f88fdcac29dfc39c1221d25d <9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73 | 3b32cf6e279597d1b6477fb89d46abf65263c139, 79fa3a19aa6114189b33e2ba1f393b0f635d7544, 359613f2fa009587154511e4842e8ab9532edd15, 9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Oct 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.