Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2026-68245 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 fe16a7e5336ae888751984e30c451fbf7cfa5df7, 1173190412fb9d12e7efce76734118d9712ff970, 5d5fb9124a2bba96a7807086d8fe0f7ce810d546 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.13% 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 fe16a7e5336ae888751984e30c451fbf7cfa5df7 or 1173190412fb9d12e7efce76734118d9712ff970 or 5d5fb9124a2bba96a7807086d8fe0f7ce810d546 or 04cc4aa3617b0ed67e859f91f09de5d896a46f3a, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | b8f67b9ddf4f8fe6dd536590712b5912ad78f99c up to, but not including, fe16a7e5336ae888751984e30c451fbf7cfa5df7; b8f67b9ddf4f8fe6dd536590712b5912ad78f99c up to, but not including, 1173190412fb9d12e7efce76734118d9712ff970; b8f67b9ddf4f8fe6dd536590712b5912ad78f99c up to, but not including, 5d5fb9124a2bba96a7807086d8fe0f7ce810d546; b8f67b9ddf4f8fe6dd536590712b5912ad78f99c up to, but not including, 04cc4aa3617b0ed67e859f91f09de5d896a46f3a; aa22d6c58505d239814b5ef8fa7da4ce43e9212b; 251840f22eff35c25de531a3fcb523df94c128c0; 6.1.191 up to, but not including, 6.2; 6.6.160 up to, but not including, 6.7; and 1 more ranges | fe16a7e5336ae888751984e30c451fbf7cfa5df7, 1173190412fb9d12e7efce76734118d9712ff970, 5d5fb9124a2bba96a7807086d8fe0f7ce810d546, 04cc4aa3617b0ed67e859f91f09de5d896a46f3a, 6.2, 6.7 |
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: fix lifetime issue of amdgpu_vm_get_task_info_pasid() The vm pointer returned from amdgpu_vm_get_vm_from_pasid() is only valid while the lock is still being held. Once xa_unlock_irqrestore is called and returned, the pointer is no longer under lock and is subject to modification. Since, the caller still dereferences vm->task_info in amdgpu_vm_get_task_info_vm() after the lock is removed, this causes a use after unlock problem. Remove the lifetime issue present in amdgpu_vm_get_task_info_pasid() through removing the amdgpu_vm_get_vm_from_pasid() function from amdgpu_vm.c and making the relevant code inline to hold the lock while it is still in use. (cherry picked from commit 9d01579f3f868b333acc901815972685989092c7)
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
Other references
Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
Spotted an error? Tell us.