CVE-2025-39958 Details
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.
A vulnerability in the Linux kernel's IOMMU handling for PCI devices can lead to improper management of device attachments during surprise removals. When a PCI device is unexpectedly hot-plugged out, attempts to attach it to the default domain as part of the teardown process can fail. This failure occurs because the hypervisor no longer recognizes the device as valid, leading to an error that prevents the attachment. As a result, the device becomes 'fenced' by the hypervisor, blocking DMA operations and rendering IOMMU translations ineffective. The vulnerability arises because the system currently does not handle such removals correctly, causing attachment processes to fail when they should be allowed to proceed.
The vulnerability has been addressed in the Linux kernel stable tree. Users can upgrade to the latest version available in this repository to apply the fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/359613f2fa009587154511e4842e8ab9532edd15 | kernel.org | Patch |
| https://git.kernel.org/stable/c/3b32cf6e279597d1b6477fb89d46abf65263c139 | kernel.org | |
| https://git.kernel.org/stable/c/79fa3a19aa6114189b33e2ba1f393b0f635d7544 | kernel.org | |
| https://git.kernel.org/stable/c/9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.2, < 6.16.9 6.17 rc1 6.17 rc2 6.17 rc3 6.17 rc4 6.17 rc5 6.17 rc6 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 21, 2026 | CVE Modified | kernel.org |
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 26, 2026 | Reanalysis | [email protected] |
| Feb 3, 2026 | Initial Analysis | [email protected] |
| Oct 9, 2025 | New CVE Received | kernel.org |