Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64117: wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0cd37e746e98ab0baa6d8b812955220775b080d6, 2fb64f94f9afb774f2fa0c7835727d7a67f89f07, 5fe97797412aa8bc0184f78379fafb594bcb7f66; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 0cd37e746e98ab0baa6d8b812955220775b080d6, 2fb64f94f9afb774f2fa0c7835727d7a67f89f07, 5fe97797412aa8bc0184f78379fafb594bcb7f66; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: capture fast-RX rate before mesh reuses skb->cb ieee80211_invoke_fast_rx() reads RX status through IEEE80211_SKB_RXCB(skb), which aliases the same skb->cb storage that ieee80211_rx_mesh_data() reuses as IEEE80211_TX_INFO. In the unicast forward path, mesh_data does: info = IEEE80211_SKB_CB(fwd_skb); memset(info, 0, sizeof(*info)); on the same skb the caller still names via rx->skb, then either queues the skb for TX (success) or kfree_skb()'s it (no-route) before returning RX_QUEUED. The caller's RX_QUEUED arm then calls sta_stats_encode_rate(status) on memory that is either zeroed (success path) or freed (no-route path). The latter is KASAN slab-use-after-free in ieee80211_prepare_and_rx_handle. Fix by encoding the rate from status before invoking ieee80211_rx_mesh_data(), so the RX_QUEUED arm consumes a value captured while status was still backed by valid memory.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 21, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64117

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.4 and later · before 7.0.11
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.4affected
    • 3468e1e0c639032a603450f0830ccabfa76f5806 and later · before 5fe97797412aa8bc0184f78379fafb594bcb7f66affected · git
    • 3468e1e0c639032a603450f0830ccabfa76f5806 and later · before 0cd37e746e98ab0baa6d8b812955220775b080d6affected · git
    • 3468e1e0c639032a603450f0830ccabfa76f5806 and later · before a2650f8461cd8ba287fee2992b36abe733c2bd5eaffected · git
    • 3468e1e0c639032a603450f0830ccabfa76f5806 and later · before 2fb64f94f9afb774f2fa0c7835727d7a67f89f07affected · git
    • 3468e1e0c639032a603450f0830ccabfa76f5806 and later · before d71c841be5d9e586ee7f36c0dc8ed4db0d9a1349affected · git
    • before 6.4not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver
    • 6.18.57 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.163.1.el8_104.18.0-553.163.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.163.1.rt7.504.el8_104.18.0-553.163.1.rt7.504.el8_10

+64

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64114Jul 19, 2026 · ipv4: raw: reject IP_HDRINCL packets with ihl < 5
    31Monitor
  • ← EarlierCVE-2026-64115Jul 19, 2026 · vsock/vmci: fix UAF when peer resets connection during handshake
    35Monitor
  • Later →CVE-2026-64118Jul 19, 2026 · qed: fix double free in qed_cxt_tables_alloc()
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0cd37e746e98ab0baa6d8b812955220775b080d6Vendor (CNA)
Linux Linux2fb64f94f9afb774f2fa0c7835727d7a67f89f07Vendor (CNA)
Linux Linux5fe97797412aa8bc0184f78379fafb594bcb7f66Vendor (CNA)
Linux Linuxa2650f8461cd8ba287fee2992b36abe733c2bd5eVendor (CNA)
Linux Linuxd71c841be5d9e586ee7f36c0dc8ed4db0d9a1349Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.163.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.0.12-1 · Debian:14Package registry (OSV)
red hat:bpftool0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+5

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records