Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2026-46157 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 e718cecb73214f53fe8f48083eb7afe9b0921103, c937a494901df8fbfaa5037a5883a7cd44282ea8, 49f9d048845be874df7997e4b1ce662de450c4b6 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 e718cecb73214f53fe8f48083eb7afe9b0921103 or c937a494901df8fbfaa5037a5883a7cd44282ea8 or 49f9d048845be874df7997e4b1ce662de450c4b6 or ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.88 or 6.18.30 or 7.0.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, e718cecb73214f53fe8f48083eb7afe9b0921103; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, c937a494901df8fbfaa5037a5883a7cd44282ea8; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 49f9d048845be874df7997e4b1ce662de450c4b6; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 6b01c1bc9a4748ab37548a700a8aaff910e298e6; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 901ac0ff15edf9503162e2cf6579bd11a30f1ed4; 2.6.12 | e718cecb73214f53fe8f48083eb7afe9b0921103, c937a494901df8fbfaa5037a5883a7cd44282ea8, 49f9d048845be874df7997e4b1ce662de450c4b6, ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1, 6b01c1bc9a4748ab37548a700a8aaff910e298e6, 901ac0ff15edf9503162e2cf6579bd11a30f1ed4 |
| Linux | Linux Kernel | 2.6.12.1 up to, but not including, 6.12.88; 6.13 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.7; 2.6.12; 7.1 | 6.12.88, 6.18.30, 7.0.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: ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger Currently the runtime.oss.trigger field may be accessed concurrently without protection, which may lead to the data race. And, in this case, it may lead to more severe problem because it's a bit field; as writing the data, it may overwrite other bit fields as well, which confuses the operation completely, as spotted by fuzzing. Fix it by covering runtime.oss.trigger bit fled also with the existing params_lock mutex in both snd_pcm_oss_get_trigger() and snd_pcm_oss_poll().
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.
- 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.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.