drm/msm/a3xx: fix error handling in a3xx_gpu_init()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/a3xx: fix error handling in a3xx_gpu_init()
These error paths returned 1 on failure, instead of a negative error code. This would lead to an Oops in the caller. A second problem is that the check for "if (ret != -ENODATA)" did not work because "ret" was set to 1.
From the CVE record · Linux
Error paths in a3xx_gpu_init() returned 1 instead of a negative error code, which could cause an Oops in the caller. The incorrect return value also prevented a check for -ENODATA from working. The input does not specify how the error paths can be reached or whether authentication or user interaction is required.
Engineers running Linux kernels with the drm/msm/a3xx component should check their versions; affected versions are not specified.