drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE
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 |
|
|
6.12.356.15.46.16In the Linux kernel, the following vulnerability has been resolved:
drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE
Calling this packet is necessary when we switch contexts because there are various pieces of state used by userspace to synchronize between BR and BV that are persistent across submits and we need to make sure that they are in a "safe" state when switching contexts. Otherwise a userspace submission in one context could cause another context to function incorrectly and hang, effectively a denial of service (although without leaking data). This was missed during initial a7xx bringup.
Patchwork: https://patchwork.freedesktop.org/patch/654924/
From the CVE record · Linux
The Linux kernel’s drm/msm/a7xx driver does not reset persistent state when switching contexts. A local userspace submission in one context can cause another context to malfunction and hang, resulting in a denial of service without leaking data.
Engineers running Linux kernels with the drm/msm/a7xx driver should check whether their kernel includes the fix; affected versions are not specified.