High 7.8Published Oct 9, 2025

CVE-2025-39958iommu/s390: Make attach succeed when the device was surprise removed

Updated under an hour ago (Oct 28, 2026, 6:00 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 21, 2026
First seen by InfoSec Signals: Oct 19, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	59bbf596791b89c7f88fdcac29dfc39c1221d25d builds before 3b32cf6e279597d1b6477fb89d46abf65263c139; from 59bbf596791b89c7f88fdcac29dfc39c1221d25d before 79fa3a19aa6114189b33e2ba1f393b0f635d7544; from 59bbf596791b89c7f88fdcac29dfc39c1221d25d before 359613f2fa009587154511e4842e8ab9532edd15; 59bbf596791b89c7f88fdcac29dfc39c1221d25d builds before 9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73	CNA record
linux linux_kernel linux:linux_kernel	from 6.2 before 6.16.9; 6.17; 6.17; 6.17; 6.17; 6.17; 6.17	NVD

References

References

https://git.kernel.org/stable/c/3b32cf6e279597d1b6477fb89d46abf65263c139
https://git.kernel.org/stable/c/79fa3a19aa6114189b33e2ba1f393b0f635d7544
https://git.kernel.org/stable/c/359613f2fa009587154511e4842e8ab9532edd15	patch
https://git.kernel.org/stable/c/9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.