First published: Wed Mar 06 2024(Updated: )
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/
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Kernel-devel | ||
Linux Kernel | <6.7.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-52586 is classified as a high-severity vulnerability affecting the Linux kernel.
To fix CVE-2023-52586, update to the latest version of the Linux kernel that patches this vulnerability.
CVE-2023-52586 affects the Direct Rendering Manager (DRM) in the Linux kernel, specifically related to mutex locking in control vblank IRQ.
The risks associated with CVE-2023-52586 include possible race conditions that could lead to system instability or denial of service.
CVE-2023-52586 was announced as part of the Linux kernel updates addressing various vulnerabilities.