Linux: Concurrent Execution using Shared Resource with Improper Synchronization
CVE-2026-52988 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 ed8d3bd8272e49ea987100de2abfb13710329a9b, 8fdd2204503ab1ce07dc000c277e2c3edf96a67b, 5593c640f9daedec8de61555c41e1019fa675aa6 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 ed8d3bd8272e49ea987100de2abfb13710329a9b or 8fdd2204503ab1ce07dc000c277e2c3edf96a67b or 5593c640f9daedec8de61555c41e1019fa675aa6 or 00e370627f2e1fb3585f9d26348b1abddc75442b, whichever matches your release line, or a later version.
- Update Linux Kernel to 7.0.10 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, ed8d3bd8272e49ea987100de2abfb13710329a9b; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, 8fdd2204503ab1ce07dc000c277e2c3edf96a67b; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, 5593c640f9daedec8de61555c41e1019fa675aa6; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, 00e370627f2e1fb3585f9d26348b1abddc75442b; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, 28ecfb3d1fe8dea70319de7051cb6718c25b5b52; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, a557816c6e38e9473d99aa9ea8c662f55fc85847; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, 1346be9379639c30877083b12747d4eacb83c24f; 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 up to, but not including, a6134e62dba2ea4f760b29d5226907f447c92400; and 1 more ranges | ed8d3bd8272e49ea987100de2abfb13710329a9b, 8fdd2204503ab1ce07dc000c277e2c3edf96a67b, 5593c640f9daedec8de61555c41e1019fa675aa6, 00e370627f2e1fb3585f9d26348b1abddc75442b, 28ecfb3d1fe8dea70319de7051cb6718c25b5b52, a557816c6e38e9473d99aa9ea8c662f55fc85847 |
| Linux | Linux Kernel | 5.8 up to, but not including, 7.0.10; 7.1 | 7.0.10 |
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
- NoneNothing can be modified.
- 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:N/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: join hook list via splice_list_rcu() in commit phase Publish new hooks in the list into the basechain/flowtable using splice_list_rcu() to ensure netlink dump list traversal via rcu is safe while concurrent ruleset update is going on.
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
- git.kernel.org/stable/c/00e370627f2e1fb3585f9d26348b1abddc75442b
- git.kernel.org/stable/c/28ecfb3d1fe8dea70319de7051cb6718c25b5b52
- git.kernel.org/stable/c/5593c640f9daedec8de61555c41e1019fa675aa6
- git.kernel.org/stable/c/8fdd2204503ab1ce07dc000c277e2c3edf96a67b
- git.kernel.org/stable/c/a557816c6e38e9473d99aa9ea8c662f55fc85847
- git.kernel.org/stable/c/ed8d3bd8272e49ea987100de2abfb13710329a9b
Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities
- 9.8 Critical severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.