drm/msm/dpu: Add mutex lock in control vblank irq
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/dpu: Add mutex lock in control vblank irq
Add a mutex lock to control vblank irq to synchronize vblank enable/disable operations happening from different threads to prevent race conditions while registering/unregistering the vblank irq callback.
v4: -Removed vblank_ctl_lock from dpu_encoder_virt, so it is only a parameter of dpu_encoder_phys. -Switch from atomic refcnt to a simple int counter as mutex has now been added v3: Mistakenly did not change wording in last version. It is done now. v2: Slightly changed wording of commit message
Patchwork: https://patchwork.freedesktop.org/patch/571854/
From the CVE record · Linux
The Linux kernel’s drm/msm/dpu component has a race condition when different threads enable or disable the vblank IRQ and register or unregister its callback. The input does not specify what an attacker could do or whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux kernels with the drm/msm/dpu component should check their kernel versions; affected versions are not specified.