CVE-2023-52586
What it is
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/
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Linux Kernel < 6.7.4
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52586.md and follow it. Check whether this project is affected by CVE-2023-52586. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/14f109bf74dd67e1d0469fed859c8e506b0df53f
- https://git.kernel.org/stable/c/45284ff733e4caf6c118aae5131eb7e7cf3eea5a
- https://git.kernel.org/stable/c/14f109bf74dd67e1d0469fed859c8e506b0df53f
- https://git.kernel.org/stable/c/45284ff733e4caf6c118aae5131eb7e7cf3eea5a
References
- https://git.kernel.org/stable/c/14f109bf74dd67e1d0469fed859c8e506b0df53f
- https://git.kernel.org/stable/c/45284ff733e4caf6c118aae5131eb7e7cf3eea5a
- https://git.kernel.org/stable/c/763ca8d84f34d1db00d5750f77e6001765916d44
- https://git.kernel.org/stable/c/f6dd625053726ea2a209282bee97218f2ec04149
- https://git.kernel.org/stable/c/14f109bf74dd67e1d0469fed859c8e506b0df53f
- https://git.kernel.org/stable/c/45284ff733e4caf6c118aae5131eb7e7cf3eea5a