Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2024-57876 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 94b33b2d7640e807869451384eb88321dd0ffbd4, d834d20d2e86c52ed5cab41763fa61e6071680ef, be826b4451fd187a7c0b04be4f8243d5df6e0450 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.16% 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 94b33b2d7640e807869451384eb88321dd0ffbd4 or d834d20d2e86c52ed5cab41763fa61e6071680ef or be826b4451fd187a7c0b04be4f8243d5df6e0450 or a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.11 or 5.16 or 6.1.120 or 6.6.66, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | b30fcedeba643ca16eaa6212c1245598b7cd830d up to, but not including, 94b33b2d7640e807869451384eb88321dd0ffbd4; 1d082618bbf3b6755b8cc68c0a8122af2842d593 up to, but not including, d834d20d2e86c52ed5cab41763fa61e6071680ef; 1d082618bbf3b6755b8cc68c0a8122af2842d593 up to, but not including, be826b4451fd187a7c0b04be4f8243d5df6e0450; 1d082618bbf3b6755b8cc68c0a8122af2842d593 up to, but not including, a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7; ee4a4282d78d96e07e714c28ca54679713fa2157; db35e49413a4d03ea0c003598803e49956f59324; a579ed4613b5a64074963988ad481e43cf3b917b; 6.1.18 up to, but not including, 6.1.120; and 4 more ranges | 94b33b2d7640e807869451384eb88321dd0ffbd4, d834d20d2e86c52ed5cab41763fa61e6071680ef, be826b4451fd187a7c0b04be4f8243d5df6e0450, a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7, 6.1.120, 5.11 |
| Linux | Linux Kernel | 5.10.173 up to, but not including, 5.11; 5.15.100 up to, but not including, 5.16; 6.1.18 up to, but not including, 6.1.120; 6.2.5 up to, but not including, 6.6.66; 6.7 up to, but not including, 6.12.5; 6.13 | 5.11, 5.16, 6.1.120, 6.6.66, 6.12.5 |
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing in drm_dp_mst_handle_down_rep() and drm_dp_mst_handle_up_req(), however this would require a bigger change. Since the fix is also needed for stable, opting for the simpler solution in this patch.
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
- 7.0 High severity
- 7.0 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.