Answer in brief
CVE-2026-98424 records a Unknown severity vulnerability in wifi: cfg80211: undo netns switch if renaming the wiphy fails. 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 | >=463d018323851a608eef52a9427b0585005c647f <96bef5667b0c4aecb1b850d2343f69b9d684abb9 || >=463d018323851a608eef52a9427b0585005c647f <739b7bf3942da4cde8eedb143d01a16ed865d1d7 || >=463d018323851a608eef52a9427b0585005c647f <a41bd1938a9bfe226d444172a7e20e4bd5097960 | 96bef5667b0c4aecb1b850d2343f69b9d684abb9, 739b7bf3942da4cde8eedb143d01a16ed865d1d7, a41bd1938a9bfe226d444172a7e20e4bd5097960 |
| Linux/Linuxgeneric | 2.6.32 | Not reported |
Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 14, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: undo netns switch if renaming the wiphy fails Once all the interfaces have been moved, cfg80211_switch_netns() moves the wiphy itself by setting its network namespace and then renaming it, which makes sysfs move it. The rename can fail (but only on allocation failures), leaving things mixed up and hitting the warning there. Ignoring it isn't great, undo the move and let the change fail in this case. If undo fails then WARN, then things would again be stuck in two different network namespaces.
Quoted source text, attributed separately from HOL analysis.