CVE-2026-98330
HighIn 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.
CVSS 3.1 score
7.0
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected versions
Linux kernel versions
2.6.32
and later are affected. Fixed in
6.18.54,
7.2.8,
7.3-rc4
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-98330?
CVE-2026-98330 is a High severity Linux kernel vulnerability with a CVSS score of 7.0 out of 10 . It affects Linux kernel versions from 2.6.32 onward and has been patched in 6.18.54, 7.2.8 and 7.3-rc4. CVE-2026-98330 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-98330?
CVE-2026-98330 has a CVSS score of 7.0 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2026-98330?
Yes. CVE-2026-98330 has been patched. Fixed versions include 6.18.54, 7.2.8 and 7.3-rc4. If you are running Linux kernel 2.6.32 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-98330 actively exploited?
No. CVE-2026-98330 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.