Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2023-52586 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 763ca8d84f34d1db00d5750f77e6001765916d44, f6dd625053726ea2a209282bee97218f2ec04149, 14f109bf74dd67e1d0469fed859c8e506b0df53f as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.23% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 763ca8d84f34d1db00d5750f77e6001765916d44 or f6dd625053726ea2a209282bee97218f2ec04149 or 14f109bf74dd67e1d0469fed859c8e506b0df53f or 45284ff733e4caf6c118aae5131eb7e7cf3eea5a, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.7.4 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef up to, but not including, 763ca8d84f34d1db00d5750f77e6001765916d44; 25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef up to, but not including, f6dd625053726ea2a209282bee97218f2ec04149; 25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef up to, but not including, 14f109bf74dd67e1d0469fed859c8e506b0df53f; 25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef up to, but not including, 45284ff733e4caf6c118aae5131eb7e7cf3eea5a; 4.19 | 763ca8d84f34d1db00d5750f77e6001765916d44, f6dd625053726ea2a209282bee97218f2ec04149, 14f109bf74dd67e1d0469fed859c8e506b0df53f, 45284ff733e4caf6c118aae5131eb7e7cf3eea5a |
| Linux | Linux Kernel | before 6.7.4 | 6.7.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.0 | High | NVD |
Official description
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/
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Concurrent Execution using Shared Resource with Improper Synchronization
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
How developers prevent this class of flaw
- In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
- Use thread-safe capabilities such as the data access abstraction in Spring.
- Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities
- 7.0 High severity
- 7.0 High severity
- 8.8 High severity
- 7.0 High severity
- 7.0 High severity
- 7.5 High severity
Spotted an error? Tell us.