CyberSecBulletin
CVE-2026-46152NVD status: Modified

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

CVE-2026-46152 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 03584528bfffb195e384698af9148b94e42e3f14, 1739fc31b4de06c5c78ce0741182770fb079091e, e131562d6f2b958148c35c98831b007f47f0e3d3 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.17% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 03584528bfffb195e384698af9148b94e42e3f14 or 1739fc31b4de06c5c78ce0741182770fb079091e or e131562d6f2b958148c35c98831b007f47f0e3d3 or 3ef44f96ccc3e06e059dec57842e366f0c4b1893, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.140 or 6.12.88 or 6.18.30 or 7.0.7, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux3468e1e0c639032a603450f0830ccabfa76f5806 up to, but not including, 03584528bfffb195e384698af9148b94e42e3f14; 3468e1e0c639032a603450f0830ccabfa76f5806 up to, but not including, 1739fc31b4de06c5c78ce0741182770fb079091e; 3468e1e0c639032a603450f0830ccabfa76f5806 up to, but not including, e131562d6f2b958148c35c98831b007f47f0e3d3; 3468e1e0c639032a603450f0830ccabfa76f5806 up to, but not including, 3ef44f96ccc3e06e059dec57842e366f0c4b1893; 3468e1e0c639032a603450f0830ccabfa76f5806 up to, but not including, 7a5b81e0c87a075afd572f659d8eb68c9c4cd2ba; 6.403584528bfffb195e384698af9148b94e42e3f14, 1739fc31b4de06c5c78ce0741182770fb079091e, e131562d6f2b958148c35c98831b007f47f0e3d3, 3ef44f96ccc3e06e059dec57842e366f0c4b1893, 7a5b81e0c87a075afd572f659d8eb68c9c4cd2ba
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10.0 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.4 Update Services for SAP SolutionsNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.6 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 6Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
LinuxLinux Kernel6.4 up to, but not including, 6.6.140; 6.7 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; 7.16.6.140, 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
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighCNA
CVSS 3.17.0HighCNA

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: drop stray 'static' from fast-RX rx_result ieee80211_invoke_fast_rx() is documented as safe for parallel RX, but its per-invocation rx_result is declared static. Concurrent callers then share one instance and can overwrite each other's result between ieee80211_rx_mesh_data() and the switch on res. That can make a packet that was queued or consumed by ieee80211_rx_mesh_data() fall through into ieee80211_rx_8023(), or make a packet that should continue return as queued. Make res an automatic variable so each invocation keeps its own result.

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).

More Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities (CWE-362)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.