# CVE-2026-98424: wifi: cfg80211: undo netns switch if renaming the wiphy fails

> A local attacker can trigger a kernel warning and potential system instability by causing a wiphy rename failure during a network namespace switch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108099, BELL-CVE-2026-98424, DEBIAN-CVE-2026-98424, GHSA-ppjv-3xmq-grw5, UBUNTU-CVE-2026-98424

## What is CVE-2026-98424?

CVE-2026-98424 is a denial of service vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-98424?


## How do I fix CVE-2026-98424?

Apply the vendor's patch.

## Is CVE-2026-98424 being exploited?

There is no known exploitation of CVE-2026-98424 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98424 and fix it if it is affected.

What it is: CVE-2026-98424 is a denial of service vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98424 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98424/ (Markdown: https://insights.sbomify.com/CVE-2026-98424/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98424
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98424
- OSV: https://osv.dev/vulnerability/CVE-2026-98424

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98424/
Summaries are generated and may contain mistakes; the official description above is the record.