iommu/s390: Implement blocking domain
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.11.116.12.26.13In 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.
From the CVE record · Linux
The Linux kernel’s s390 IOMMU handling can crash when a PCI device is unexpectedly hot-unplugged. During removal, attaching the default domain can fail, leaving a NULL domain pointer and a use-after-free condition. The input does not establish an attacker path or authentication requirements.
Engineers running the Linux kernel on s390 systems with PCI devices should check their kernel version; affected versions are not specified.