CVE-2026-64568: wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure
Noroxi assessment
Priority: Monitor (action score 31/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0ace76e410d7f7d813b605825a3e593a79c3958f, 1d067abcd37062426c59ec73dbc4e87a63f33fea, ca27a81cd77b698e5eb586a011bee6800c7ee4bd.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0ace76e410d7f7d813b605825a3e593a79c3958f, 1d067abcd37062426c59ec73dbc4e87a63f33fea, ca27a81cd77b698e5eb586a011bee6800c7ee4bd 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: fix unsol_bcast_probe_resp double free on alloc failure ieee80211_set_unsol_bcast_probe_resp() calls kfree_rcu() on the old template before allocating the replacement. If the kzalloc() then fails, it returns -ENOMEM while link->u.ap.unsol_bcast_probe_resp still points at the object already queued for freeing. A later update or AP teardown re-queues that same rcu_head; the second free is caught by KASAN when the RCU sheaf is processed in softirq: BUG: KASAN: double-free in rcu_free_sheaf (mm/slub.c:5850) Free of addr ffff88800d06f300 by task exploit/145 ... __rcu_free_sheaf_prepare (mm/slub.c:2634 mm/slub.c:2940) rcu_free_sheaf (mm/slub.c:5850) rcu_core (kernel/rcu/tree.c:2617 kernel/rcu/tree.c:2869) handle_softirqs (kernel/softirq.c:622) The buggy address belongs to the cache kmalloc-128 of size 128 Queue the old object for kfree_rcu() only after the new one is published, matching ieee80211_set_probe_resp() and ieee80211_set_s1g_short_beacon().
- Published
- Aug 5, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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.7affected
- 3b1c256eb4aedfc71dd97d5951ccff824b41d628 and later · before ca27a81cd77b698e5eb586a011bee6800c7ee4bdaffected · git
- 3b1c256eb4aedfc71dd97d5951ccff824b41d628 and later · before d62b55b7c7dc62887d7fd5648fb38f0bfaef53aeaffected · git
- 3b1c256eb4aedfc71dd97d5951ccff824b41d628 and later · before 0ace76e410d7f7d813b605825a3e593a79c3958faffected · git
- 3b1c256eb4aedfc71dd97d5951ccff824b41d628 and later · before 1d067abcd37062426c59ec73dbc4e87a63f33feaaffected · git
- before 6.7not affected · semver
- 6.12.101 and later · up to and including 6.12.*not affected · semver
- 6.18.42 and later · up to and including 6.18.*not affected · semver
- 7.1.6 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
| SUSE:Linux Micro 6.0 | kernel-default | before 6.4.0-159998.54.1 | 6.4.0-159998.54.1 |
| SUSE:Linux Micro 6.0 | kernel-default-base | before 6.4.0-159998.54.1.159998.21.40 | 6.4.0-159998.54.1.159998.21.40 |
| SUSE:Linux Micro 6.0 | kernel-kvmsmall | before 6.4.0-159998.54.1 | 6.4.0-159998.54.1 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-159998.54.1 | 6.4.0-159998.54.1 |
| SUSE:Linux Micro 6.0 | kernel-source | before 6.4.0-159998.54.1 | 6.4.0-159998.54.1 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-159998.54.1 | 6.4.0-159998.54.1 |
| SUSE:Linux Micro 6.1 | kernel-default-base | before 6.4.0-159998.54.1.159998.21.39 | 6.4.0-159998.54.1.159998.21.39 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64566Aug 5, 2026 · xfrm: iptfs: propagate SKBFL_SHARED_FRAG in iptfs_skb_add_frags()39Monitor
- ← EarlierCVE-2026-64567Aug 5, 2026 · btrfs: reject free space cache with more entries than pages31Monitor
- Later →CVE-2026-64569Aug 5, 2026 · mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ace76e410d7f7d813b605825a3e593a79c3958f | Vendor (CNA) |
| Linux Linux | 1d067abcd37062426c59ec73dbc4e87a63f33fea | Vendor (CNA) |
| Linux Linux | ca27a81cd77b698e5eb586a011bee6800c7ee4bd | Vendor (CNA) |
| Linux Linux | d62b55b7c7dc62887d7fd5648fb38f0bfaef53ae | Vendor (CNA) |
| debian:linux | 6.12.101-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-159998.54.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-159998.54.1.159998.21.40 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.4.0-159998.54.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-159998.54.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-159998.54.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-159998.54.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
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.
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.
Credits
All researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0742 · Aug 5, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.