CVE-2026-72004

wifi: mac80211: fix memory leak in ieee80211_register_hw()

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 17, 2026 at 06:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix memory leak in ieee80211_register_hw() If kmemdup() fails while copying supported band structures, the error path jumps to fail_rate. This skips rate_control_deinitialize() and leaks the initialized local->rate_ctrl. Fix this by adding a fail_band label that shares the rate-control cleanup path before falling through to the remaining teardown. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc7. An x86_64 allyesconfig build showed no new warnings. As we do not have a suitable mac80211 device/driver combination to test with, no runtime testing was able to be performed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.20 ≤ v < 5.10.2614.20 ≤ v < 5.15.2124.20 ≤ v < 6.1.1784.20 ≤ v < 6.12.974.20 ≤ v < 6.18.404.20 ≤ v < 6.6.1454.20 ≤ v < 7.1.54.20 ≤ v < 7.24.209b4a4faf9d37990ac4f8110dd944b27b42d5df
Vendor states this is fixed in 08b71bd92317f99642b842cfc0d30200868162fc (fixed)
Vendor states this is fixed in 3d8b9b290421c3cd505fcd2f551f143f8142786a (fixed)
Vendor states this is fixed in 45e9ac538cdff7bce656d731114a64eda85af0d7 (fixed)
Vendor states this is fixed in 95fc02722edde02946d0d475221f2b2054d3d8ba (fixed)
Vendor states this is fixed in a02b52fe54f7b5107aefa1ce28c2f69749c57616 (fixed)
Vendor states this is fixed in a7584f261e64fe14e45bdf70f343e16c1ee3a037 (fixed)
Vendor states this is fixed in bdc0b8bfdc142439d6708b072e8159eb515ee7b0 (fixed)
Vendor states this is fixed in f01eec75fd372961550b928902f3a2c11fca1daf (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card