Linux: Race Condition within a Thread
CVE-2026-46181 is a high-severity race condition within a thread 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 654aeddbc6e0f6e56531985bb12328ab4230c6c1, 2d8b30b496bc53e961ba7415fd629fc27813017c, f0dbd9355ce1e93808541260c7ffab7956df9233 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.14% 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 654aeddbc6e0f6e56531985bb12328ab4230c6c1 or 2d8b30b496bc53e961ba7415fd629fc27813017c or f0dbd9355ce1e93808541260c7ffab7956df9233 or 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, whichever matches your release line, or a later version.
- Update Linux Kernel to 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 | 30353bfc43a1602c020f31d95cf27182ffd23824 up to, but not including, 654aeddbc6e0f6e56531985bb12328ab4230c6c1; 30353bfc43a1602c020f31d95cf27182ffd23824 up to, but not including, 2d8b30b496bc53e961ba7415fd629fc27813017c; 30353bfc43a1602c020f31d95cf27182ffd23824 up to, but not including, f0dbd9355ce1e93808541260c7ffab7956df9233; 30353bfc43a1602c020f31d95cf27182ffd23824 up to, but not including, 1e2a44875b6afb4add1115f7f3351dcbeb6f273d; 30353bfc43a1602c020f31d95cf27182ffd23824 up to, but not including, 8b7833f3bce35cb0d01c1503781523c099c675f0; 30353bfc43a1602c020f31d95cf27182ffd23824 up to, but not including, c9341307ea16b9395c2e4c9c94d8499d91fe31d0; 4.9 | 654aeddbc6e0f6e56531985bb12328ab4230c6c1, 2d8b30b496bc53e961ba7415fd629fc27813017c, f0dbd9355ce1e93808541260c7ffab7956df9233, 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, 8b7833f3bce35cb0d01c1503781523c099c675f0, c9341307ea16b9395c2e4c9c94d8499d91fe31d0 |
| Red Hat | Red Hat Enterprise Linux 7 Extended Lifecycle Support | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8.8 Telecommunications Update Service | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9.6 Extended Update Support | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 6 | Not specified in the record | Not stated |
| Linux | Linux Kernel | 4.9 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.7; 7.1 | 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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.0 | High | CNA |
Official description
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() Sashiko points out the radix_tree itself is RCU safe, but nothing ever frees the mlx4_srq struct with RCU, and it isn't even accessed within the RCU critical section. It also will crash if an event is delivered before the srq object is finished initializing. Use the spinlock since it isn't easy to make RCU work, use refcount_inc_not_zero() to protect against partially initialized objects, and order the refcount_set() to be after the srq is fully initialized.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Race Condition within a Thread
If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.
How developers prevent this class of flaw
- Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.
- Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.
More Race Condition within a Thread vulnerabilities (CWE-366)
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
- git.kernel.org/stable/c/2d8b30b496bc53e961ba7415fd629fc27813017c
- git.kernel.org/stable/c/654aeddbc6e0f6e56531985bb12328ab4230c6c1
- git.kernel.org/stable/c/f0dbd9355ce1e93808541260c7ffab7956df9233
- access.redhat.com/errata/RHSA-2026:25120
- access.redhat.com/errata/RHSA-2026:25121
- access.redhat.com/errata/RHSA-2026:25217
- access.redhat.com/errata/RHSA-2026:33900
- access.redhat.com/errata/RHSA-2026:34094
- access.redhat.com/errata/RHSA-2026:34095
- access.redhat.com/errata/RHSA-2026:34443
- access.redhat.com/errata/RHSA-2026:35863
- access.redhat.com/errata/RHSA-2026:35894
- access.redhat.com/errata/RHSA-2026:35896
- access.redhat.com/errata/RHSA-2026:36216
- access.redhat.com/errata/RHSA-2026:41236
Recent Race Condition within a Thread vulnerabilities
- 9.8 Critical severity
- 8.7 High severity
- 7.0 High severity
Spotted an error? Tell us.