drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 · < e8ac2060597a5768e4699bb61d604b4c09927b85| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs
There are some cases, such as the one uncovered by Commit 46d4efcccc68 ("drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails") where
msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);
is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.
Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).
Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.
Patchwork: https://patchwork.freedesktop.org/patch/602742/
From the CVE record · Linux
The Linux kernel’s drm/msm/adreno driver can dereference a null GPU device pointer during cleanup if initialization fails, including when speedbin data exists but opp-supported-hw is missing from the device tree. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the drm/msm/adreno driver should check their builds; affected versions are not specified.