iommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2f75cb27bef43c8692b0f5e471e5632f6a9beb99, Kernel 38e8844005e6068f336a3ad45451a562a0040ca1, Kernel 69f9d2d37d1207c5a73dac52a4ce1361ead707f5 and 3 more.
In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group Currently, mtk_iommu calls during probe iommu_device_register before the hw_list from driver data is initialized. Since iommu probing issue fix, it leads to NULL pointer dereference in mtk_iommu_device_group when hw_list is accessed with list_first_entry (not null safe). So, change the call order to ensure iommu_device_register is called after the driver data are initialized.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.19, >=9e3a2a64365318a743e3c0b028952d2cdbaf2b0c <2f75cb27bef43c8692b0f5e471e5632f6a9beb99, >=9e3a2a64365318a743e3c0b028952d2cdbaf2b0c <38e8844005e6068f336a3ad45451a562a0040ca1, >=9e3a2a64365318a743e3c0b028952d2cdbaf2b0c <69f9d2d37d1207c5a73dac52a4ce1361ead707f5, >=9e3a2a64365318a743e3c0b028952d2cdbaf2b0c <6abd09bed43b8d83d461e0fb5b9a200a06aa8a27, >=9e3a2a64365318a743e3c0b028952d2cdbaf2b0c <a0842539e8ef9386c070156103aff888e558a60c, >=9e3a2a64365318a743e3c0b028952d2cdbaf2b0c <ce7d3b2f6f393fa35f0ea12861b83a1ca28b295c | 2f75cb27bef43c8692b0f5e471e5632f6a9beb99, 38e8844005e6068f336a3ad45451a562a0040ca1, 69f9d2d37d1207c5a73dac52a4ce1361ead707f5, 6abd09bed43b8d83d461e0fb5b9a200a06aa8a27, a0842539e8ef9386c070156103aff888e558a60c, ce7d3b2f6f393fa35f0ea12861b83a1ca28b295c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket