iommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9e3a2a64365318a743e3c0b028952d2cdbaf2b0c · < 38e8844005e6068f336a3ad45451a562a0040ca1| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s MediaTek IOMMU driver can dereference a NULL pointer during device probing because it registers the IOMMU device before initializing driver data. The input does not describe an attacker path or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the MediaTek IOMMU driver should check whether their kernel includes the fix; affected versions are not specified.