dbcve.org
Linux KernelOperating system · Linux

CVE-2026-46152

HIGH · 8.8 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 6.6.140 / 6.12.88 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A race condition exists in the Linux kernel's mac80211 wireless driver where a 'static' variable in ieee80211_invoke_fast_rx() is incorrectly shared between concurrent RX path callers. This causes result overwrites between ieee80211_rx_mesh_data() and the switch statement, potentially allowing packets queued by mesh processing to fall through to the 802.3 handler or causing packets that should continue to be incorrectly marked as queued.

MitigationApply the Linux kernel patch that removes the 'static' keyword from the rx_result variable in ieee80211_invoke_fast_rx() to make it an automatic stack variable, ensuring each concurrent invocation maintains its own result state.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.4, < 6.6.140>= 6.7, < 6.12.88>= 6.13, < 6.18.30>= 6.19, < 7.0.7= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the running Linux kernel version
    Run 'uname -r' or check /proc/version to get the kernel version string
    Affected if The version falls within any of the affected ranges: >= 6.4 and < 6.6.140, >= 6.7 and < 6.12.88, >= 6.13 and < 6.18.30, >= 6.19 and < 7.0.7, or equals 7.1
  2. Confirm mac80211 wireless driver is in use
    Check if wireless hardware is present and active: run 'ip link show' to list network interfaces, then check 'iwconfig' or 'iw dev' for wireless interfaces, or verify mac80211 module is loaded via 'lsmod | grep mac80211'
    Affected if Wireless interfaces using the mac80211 driver (such as Wi-Fi adapters) are active on the system
  3. Verify the vulnerability exists in the kernel source
    If kernel source is available, search for the static 'rx_result' variable in the ieee80211_invoke_fast_rx() function within net/mac80211/rx.c
    Affected if The static variable 'rx_result' remains as a static declaration rather than being converted to a stack-allocated automatic variable

The system is affected if it runs a vulnerable kernel version within the specified ranges AND utilizes mac80211 wireless functionality, since the race condition requires concurrent RX operations on the wireless interface to trigger the packet mishandling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.140 / 6.12.88 / 6.18.30 or later
Fixed in 6.6.1406.12.886.18.30
Vendor patch git.kernel.org →
Interim mitigation

Apply the Linux kernel patch that removes the 'static' keyword from the rx_result variable in ieee80211_invoke_fast_rx() to make it an automatic stack variable, ensuring each concurrent invocation maintains its own result state.

Recommended fix High confidence

Upgrade to one of: Linux kernel 6.6.140+, 6.12.88+, 6.18.30+, or 7.0.7+ (depending on which stable branch you follow)

  1. Identify the currently running Linux kernel version using 'uname -r'
  2. Determine which version range your current kernel falls into from the affected versions: >= 6.4 to < 6.6.140, >= 6.7 to < 6.12.88, >= 6.13 to < 6.18.30, or >= 6.19 to < 7.0.7
  3. Upgrade the Linux kernel to a version that includes the fix: upgrade to 6.6.140 or later, 6.12.88 or later, 6.18.30 or later, or 7.0.7 or later
  4. After kernel upgrade, reboot the system to load the fixed kernel
  5. Verify the fix is applied by checking the kernel version and confirming the commit 03584528bfff is included
Caveat Kernel upgrades may require matching hardware drivers and could require system reboot; ensure compatibility with installed modules and hardware before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46152 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data