Answer in brief
CVE-2026-72004 records a Unknown severity vulnerability in wifi: mac80211: fix memory leak in ieee80211_register_hw(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72004 records a Unknown severity vulnerability in wifi: mac80211: fix memory leak in ieee80211_register_hw(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <f01eec75fd372961550b928902f3a2c11fca1daf || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <3d8b9b290421c3cd505fcd2f551f143f8142786a || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <08b71bd92317f99642b842cfc0d30200868162fc || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <a02b52fe54f7b5107aefa1ce28c2f69749c57616 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <45e9ac538cdff7bce656d731114a64eda85af0d7 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <bdc0b8bfdc142439d6708b072e8159eb515ee7b0 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <a7584f261e64fe14e45bdf70f343e16c1ee3a037 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <95fc02722edde02946d0d475221f2b2054d3d8ba | f01eec75fd372961550b928902f3a2c11fca1daf, 3d8b9b290421c3cd505fcd2f551f143f8142786a, 08b71bd92317f99642b842cfc0d30200868162fc, a02b52fe54f7b5107aefa1ce28c2f69749c57616, 45e9ac538cdff7bce656d731114a64eda85af0d7, bdc0b8bfdc142439d6708b072e8159eb515ee7b0, a7584f261e64fe14e45bdf70f343e16c1ee3a037, 95fc02722edde02946d0d475221f2b2054d3d8ba |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <f01eec75fd372961550b928902f3a2c11fca1daf || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <3d8b9b290421c3cd505fcd2f551f143f8142786a || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <08b71bd92317f99642b842cfc0d30200868162fc || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <a02b52fe54f7b5107aefa1ce28c2f69749c57616 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <45e9ac538cdff7bce656d731114a64eda85af0d7 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <bdc0b8bfdc142439d6708b072e8159eb515ee7b0 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <a7584f261e64fe14e45bdf70f343e16c1ee3a037 || >=09b4a4faf9d037990ac4f8110dd944b27b42d5df <95fc02722edde02946d0d475221f2b2054d3d8ba | f01eec75fd372961550b928902f3a2c11fca1daf, 3d8b9b290421c3cd505fcd2f551f143f8142786a, 08b71bd92317f99642b842cfc0d30200868162fc, a02b52fe54f7b5107aefa1ce28c2f69749c57616, 45e9ac538cdff7bce656d731114a64eda85af0d7, bdc0b8bfdc142439d6708b072e8159eb515ee7b0, a7584f261e64fe14e45bdf70f343e16c1ee3a037, 95fc02722edde02946d0d475221f2b2054d3d8ba |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.