In the Linux kernel, the following vulnerability has been resolved:
iommu/s390: Implement blocking domain
This fixes a crash when surprise hot-unplugging a PCI device. This crash
happens because during hot-unplug __iommu_group_set_domain_nofail()
attaching the default domain fails when the platform no longer
recognizes the device as it has already been removed and we end up with
a NULL domain pointer and UAF. This is exactly the case referred to in
the second comment in __iommu_device_set_domain() and just as stated
there if we can instead attach the blocking domain the UAF is prevented
as this can handle the already removed device. Implement the blocking
domain to use this handling. With this change, the crash is fixed but
we still hit a warning attempting to change DMA ownership on a blocked
device.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can crash affected s390 systems when a PCI device is unexpectedly removed. The kernel may retain and use invalid memory while changing the device’s IOMMU domain. The supplied assessment rates it high severity, but exposure depends on the s390 architecture and surprise PCI hot-unplug conditions.
Executive priority
Prioritize affected s390 systems that permit local untrusted access or operational PCI hot-unplug. Remediate through supported kernel updates on a high-priority schedule. Other architectures are not identified as affected in the supplied evidence, so validate scope before broader emergency action.
Technical view
During surprise PCI hot-unplug, attaching the default IOMMU domain can fail because the platform no longer recognizes the removed device. The resulting NULL domain pointer and use-after-free condition can crash the kernel. The referenced correction implements a blocking domain that safely handles the removed device, although the source notes a remaining warning.
Likely exposure
Likely exposure is limited to affected Linux kernel versions on s390 systems where PCI devices can be surprise hot-unplugged. The supplied CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. Exact distribution-specific exposure is not established by the bundle.
Exploitation context
The supplied record does not list this CVE in KEV and provides no evidence of active exploitation or a public exploit. A crash is documented; broader confidentiality and integrity consequences are represented in the 7.8 CVSS assessment but are not demonstrated in the supplied sources.
Researcher notes
CWE-416 applies. The failure path begins when default-domain attachment cannot recognize an already removed PCI device, leaving unsafe domain state. The blocking domain prevents the documented use-after-free crash. The source acknowledges a warning remains when DMA ownership changes are attempted on the blocked device; its security significance is not established.
Mitigation direction
Check the system or distribution vendor’s advisory for affected and corrected kernel packages.
Apply a vendor-supported kernel containing the referenced s390 IOMMU blocking-domain correction.
Restrict unnecessary local access to affected s390 systems until remediation is complete.
Avoid surprise PCI hot-unplug where operationally feasible pending remediation.
Validation and detection
Inventory Linux kernel versions and identify systems using the s390 architecture.
Compare installed kernels with vendor advisories and the referenced stable kernel commits.
Confirm the remediated kernel is running after installation and reboot.
Review kernel logs for IOMMU, PCI hot-unplug, NULL-pointer, or use-after-free warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.