iommu/s390: Implement blocking domain
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3be34fa1cdbf180c1a948cfededfdf2cdc497199, Kernel bd89d94f3ea6fdaee983cbc69226a00b9bde6d59 and Kernel ecda483339a5151e3ca30d6b82691ef6f1d17912.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.7, >=c76c067e488ccd55734c3e750799caf2c5956db6 <3be34fa1cdbf180c1a948cfededfdf2cdc497199, >=c76c067e488ccd55734c3e750799caf2c5956db6 <bd89d94f3ea6fdaee983cbc69226a00b9bde6d59, >=c76c067e488ccd55734c3e750799caf2c5956db6 <ecda483339a5151e3ca30d6b82691ef6f1d17912 | 3be34fa1cdbf180c1a948cfededfdf2cdc497199, bd89d94f3ea6fdaee983cbc69226a00b9bde6d59, ecda483339a5151e3ca30d6b82691ef6f1d17912 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket