Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2023-52825 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 7d43cdd22cd81a2b079e864c4321b9aba4c6af34, 50f35a907c4f9ed431fd3dbb8b871ef1cbb0718e, c772eacbd6d0845fc922af8716bb9d29ae27b8cf 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.18% 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 7d43cdd22cd81a2b079e864c4321b9aba4c6af34 or 50f35a907c4f9ed431fd3dbb8b871ef1cbb0718e or c772eacbd6d0845fc922af8716bb9d29ae27b8cf or fc0210720127cc6302e6d6f3de48f49c3fcf5659, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.140 or 6.1.64 or 6.5.13 or 6.6.3, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | e49fe4040a10c1cd3b215c511f658d15aa7c8be9 up to, but not including, 7d43cdd22cd81a2b079e864c4321b9aba4c6af34; e49fe4040a10c1cd3b215c511f658d15aa7c8be9 up to, but not including, 50f35a907c4f9ed431fd3dbb8b871ef1cbb0718e; e49fe4040a10c1cd3b215c511f658d15aa7c8be9 up to, but not including, c772eacbd6d0845fc922af8716bb9d29ae27b8cf; e49fe4040a10c1cd3b215c511f658d15aa7c8be9 up to, but not including, fc0210720127cc6302e6d6f3de48f49c3fcf5659; e49fe4040a10c1cd3b215c511f658d15aa7c8be9 up to, but not including, 709c348261618da7ed89d6c303e2ceb9e453ba74; 5.14 | 7d43cdd22cd81a2b079e864c4321b9aba4c6af34, 50f35a907c4f9ed431fd3dbb8b871ef1cbb0718e, c772eacbd6d0845fc922af8716bb9d29ae27b8cf, fc0210720127cc6302e6d6f3de48f49c3fcf5659, 709c348261618da7ed89d6c303e2ceb9e453ba74 |
| Linux | Linux Kernel | before 5.15.140; 5.16 up to, but not including, 6.1.64; 6.2 up to, but not including, 6.5.13; 6.6 up to, but not including, 6.6.3 | 5.15.140, 6.1.64, 6.5.13, 6.6.3 |
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
- LowNo special conditions are needed; the attack works reliably.
- 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:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 5.5 | Medium | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix a race condition of vram buffer unref in svm code prange->svm_bo unref can happen in both mmu callback and a callback after migrate to system ram. Both are async call in different tasks. Sync svm_bo unref operation to avoid random "use-after-free".
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
- git.kernel.org/stable/c/50f35a907c4f9ed431fd3dbb8b871ef1cbb0718e
- git.kernel.org/stable/c/709c348261618da7ed89d6c303e2ceb9e453ba74
- git.kernel.org/stable/c/7d43cdd22cd81a2b079e864c4321b9aba4c6af34
- git.kernel.org/stable/c/c772eacbd6d0845fc922af8716bb9d29ae27b8cf
- git.kernel.org/stable/c/fc0210720127cc6302e6d6f3de48f49c3fcf5659
Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities
- 7.8 High severity
- 7.0 High severity
- 7.3 High severity
- 7.0 High severity
- 7.0 High severity
- 8.1 High severity
Spotted an error? Tell us.