iommu/s390: Fix memory corruption when using identity 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 17a58caf3863163c4a84a218a9649be2c8061443 and Kernel b3506e9bcc777ed6af2ab631c86a9990ed97b474.
In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Fix memory corruption when using identity domain zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero'd initially and read on-demand later via a sysfs read. These counters aren't necessary for the identity domain; just return NULL in this case. This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=64af12c6ec3afd7d44bc8b2044eee59f98059087 <17a58caf3863163c4a84a218a9649be2c8061443, >=64af12c6ec3afd7d44bc8b2044eee59f98059087 <b3506e9bcc777ed6af2ab631c86a9990ed97b474 | 17a58caf3863163c4a84a218a9649be2c8061443, b3506e9bcc777ed6af2ab631c86a9990ed97b474 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket