Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2026-45862 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 cd75e77125c8a51754ca4cd60b4ca083ed735d1d, 0616137b70e6d9a547d4b60df8e1b64e36d83661, 36990407cdd257473607e33802d00e978af2759e 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 cd75e77125c8a51754ca4cd60b4ca083ed735d1d or 0616137b70e6d9a547d4b60df8e1b64e36d83661 or 36990407cdd257473607e33802d00e978af2759e or c93f23375d8c410954b0df825e814b632fd62b9d, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.5 or 5.10.252 or 5.15.202 or 6.1.165, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 7e00b52c8cdd9d3a985d63d72ecae7bde6314883 up to, but not including, cd75e77125c8a51754ca4cd60b4ca083ed735d1d; 5c65f097124770c3e5b9b83ed1a8b68c119bc7b5 up to, but not including, 0616137b70e6d9a547d4b60df8e1b64e36d83661; 2bed9455db7cc0ab7ece6b3d846472097b52855a up to, but not including, 36990407cdd257473607e33802d00e978af2759e; 194b3348bdbb7db65375c72f3f774aee4cc6614e up to, but not including, c93f23375d8c410954b0df825e814b632fd62b9d; 194b3348bdbb7db65375c72f3f774aee4cc6614e up to, but not including, 5962c30a6f05ea1ab73f039e235bb30716243517; 194b3348bdbb7db65375c72f3f774aee4cc6614e up to, but not including, 36244dfd3853f7bf89d03b8e90d56b23ce7fbc16; 194b3348bdbb7db65375c72f3f774aee4cc6614e up to, but not including, d15cda135148ea7ba929cfdbcf208182bc29a7aa; 194b3348bdbb7db65375c72f3f774aee4cc6614e up to, but not including, 22d169bdd2849fe6bd18c2643742e1c02be6451c; and 8 more ranges | cd75e77125c8a51754ca4cd60b4ca083ed735d1d, 0616137b70e6d9a547d4b60df8e1b64e36d83661, 36990407cdd257473607e33802d00e978af2759e, c93f23375d8c410954b0df825e814b632fd62b9d, 5962c30a6f05ea1ab73f039e235bb30716243517, 36244dfd3853f7bf89d03b8e90d56b23ce7fbc16 |
| Linux | Linux Kernel | 5.4.237 up to, but not including, 5.5; 5.10.175 up to, but not including, 5.10.252; 5.15.103 up to, but not including, 5.15.202; 6.1.16 up to, but not including, 6.1.165; 6.2.3 up to, but not including, 6.6.128; 6.7 up to, but not including, 6.12.75; 6.13 up to, but not including, 6.18.14; 6.19 up to, but not including, 6.19.4 | 5.5, 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75 |
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
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- 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:C/C:H/I:H/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Flush cache for PASID table before using it When writing the address of a freshly allocated zero-initialized PASID table to a PASID directory entry, do that after the CPU cache flush for this PASID table, not before it, to avoid the time window when this PASID table may be already used by non-coherent IOMMU hardware while its contents in RAM is still some random old data, not zero-initialized.
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
- git.kernel.org/stable/c/0616137b70e6d9a547d4b60df8e1b64e36d83661
- git.kernel.org/stable/c/22d169bdd2849fe6bd18c2643742e1c02be6451c
- git.kernel.org/stable/c/36244dfd3853f7bf89d03b8e90d56b23ce7fbc16
- git.kernel.org/stable/c/36990407cdd257473607e33802d00e978af2759e
- git.kernel.org/stable/c/5962c30a6f05ea1ab73f039e235bb30716243517
- git.kernel.org/stable/c/c93f23375d8c410954b0df825e814b632fd62b9d
- git.kernel.org/stable/c/cd75e77125c8a51754ca4cd60b4ca083ed735d1d
- git.kernel.org/stable/c/d15cda135148ea7ba929cfdbcf208182bc29a7aa
Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities
- 7.5 High severity
- 7.8 High severity
- 8.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.