Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2026-46311 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 2da62dbb4169e758c0b1a9378b39a373bf4fb111, 336a9186f3a4b65bbd865d93936605ac8a1a3991, 6da7b1242da4455b11c24ce667d1cab1a348c8ea 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.1% 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 2da62dbb4169e758c0b1a9378b39a373bf4fb111 or 336a9186f3a4b65bbd865d93936605ac8a1a3991 or 6da7b1242da4455b11c24ce667d1cab1a348c8ea, whichever matches your release line, or a later version.
- Update Linux Kernel to 7.0.9 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 5fb2f7fc21a3668e5794cc0d153641b9719713e1 up to, but not including, 2da62dbb4169e758c0b1a9378b39a373bf4fb111; 5fb2f7fc21a3668e5794cc0d153641b9719713e1 up to, but not including, 336a9186f3a4b65bbd865d93936605ac8a1a3991; 5fb2f7fc21a3668e5794cc0d153641b9719713e1 up to, but not including, 6da7b1242da4455b11c24ce667d1cab1a348c8ea; 6.16 | 2da62dbb4169e758c0b1a9378b39a373bf4fb111, 336a9186f3a4b65bbd865d93936605ac8a1a3991, 6da7b1242da4455b11c24ce667d1cab1a348c8ea |
| Linux | Linux Kernel | 6.16 up to, but not including, 7.0.9; 7.1 | 7.0.9 |
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: fix access to stale wptr mapping Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly. This fixes the security issue of unmap the wptr_obj while a queue creation is in progress and passing other bo at same address. (cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)
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: total).
- 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.8 High severity
- 8.3 High severity
- 7.5 High severity
- 7.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.