drm/vc4: kms: Clear the HVS FIFO commit pointer once done
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/vc4: kms: Clear the HVS FIFO commit pointer once done
Commit 9ec03d7f1ed3 ("drm/vc4: kms: Wait on previous FIFO users before a commit") introduced a wait on the previous commit done on a given HVS FIFO.
However, we never cleared that pointer once done. Since drm_crtc_commit_put can free the drm_crtc_commit structure directly if we were the last user, this means that it can lead to a use-after free if we were to duplicate the state, and that stale pointer would even be copied to the new state.
Set the pointer to NULL once we're done with the wait so that we don't carry over a pointer to a free'd structure.
From the CVE record · Linux
The Linux kernel's drm/vc4 KMS code can retain a pointer to a freed commit structure after waiting on a previous HVS FIFO commit. If the state is duplicated, the stale pointer can be copied into the new state, leading to a use-after-free. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with the affected drm/vc4 KMS code should check their kernel versions; affected versions are not specified.