7.8

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

Modified
AliasesUBUNTU-CVE-2025-39958DEBIAN-CVE-2025-39958CGA-2vhx-f8rh-7cp8
Published 09-10-2025Last modified 21-10-2026

Vulnerability summary

CVE-2025-39958 is a high (CVSS 7.8) vulnerability in linux. EPSS estimates a 0.19% chance of exploitation in the next 30 days, higher than 8.8% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.8, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.8/10
010
High · v3.1 (NVD)
EPSS score
0.19%
0%100%
Low · +0.05 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 2

Timeline

  1. 09-10-2025
    PublishedVulnerability first disclosed.
  2. 21-10-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.19%

Chance of exploitation in the next 30 days

Percentile

9%

Versus all other CVEs

30-day change

Increase +0.05 pp

From 0.14% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu124 products
  • linuxAll versions (No fix recorded)
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded)
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard5 products
  • linux-aws-6.12< 6.12.72-r1 | < 6.12.72-r0 | < 6.12.77-r2 | < 6.12.77-r0 | < 6.12.74-r0 | < 6.12.77-r1 | < 6.12.76-r0 | < 6.12.70-r0 | < 6.12.69-r0 | < 6.12.80-r0 | < 6.12.78-r0 | < 6.12.74-r1 | < 6.12.71-r0 | < 6.12.68-r1
  • linux-azure-6.12< 6.12.77-r0 | < 6.12.78-r0 | < 6.12.77-r1 | < 6.12.77-r2 | < 6.12.80-r0 | < 6.12.74-r1 | < 6.12.72-r0 | < 6.12.69-r0 | < 6.12.71-r0 | < 6.12.76-r0 | < 6.12.70-r0 | < 6.12.74-r0
  • linux-gcp-6.12< 6.12.77-r0 | < 6.12.71-r0 | < 6.12.77-r1 | < 6.12.72-r0 | < 6.12.74-r1 | < 6.12.80-r0 | < 6.12.76-r0 | < 6.12.74-r0 | < 6.12.78-r0 | < 6.12.69-r0 | < 6.12.70-r0 | < 6.12.77-r2
  • linux-qemu-6.12< 6.12.71-r0 | < 6.12.78-r0 | < 6.12.70-r0 | < 6.12.72-r0 | < 6.12.77-r2 | < 6.12.77-r0 | < 6.12.74-r0 | < 6.12.76-r0 | < 6.12.69-r0 | < 6.12.74-r1 | < 6.12.77-r1 | < 6.12.80-r0
  • linux-vmware-6.12< 6.12.77-r0 | < 6.12.78-r0 | < 6.12.69-r0 | < 6.12.76-r0 | < 6.12.74-r0 | < 6.12.72-r0 | < 6.12.77-r2 | < 6.12.71-r0 | < 6.12.70-r0 | < 6.12.80-r0 | < 6.12.74-r1 | < 6.12.77-r1
Linux2 products
  • linux≥ 59bbf596791b89c7f88fdcac29dfc39c1221d25d, < 3b32cf6e279597d1b6477fb89d46abf65263c139 | ≥ 59bbf596791b89c7f88fdcac29dfc39c1221d25d, < 79fa3a19aa6114189b33e2ba1f393b0f635d7544 | ≥ 59bbf596791b89c7f88fdcac29dfc39c1221d25d, < 359613f2fa009587154511e4842e8ab9532edd15 | ≥ 59bbf596791b89c7f88fdcac29dfc39c1221d25d, < 9ffaf5229055fcfbb3b3d6f1c7e58d63715c3f73 | 6.2
  • 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
Debian1 product
  • linuxAll versions (No fix recorded) | < 6.12.115-2 | < 6.16.9-1

4 vendors · 132 products

References

8 links