CVE Tools

CVE-2026-98424

wifi: cfg80211: undo netns switch if renaming the wiphy fails

No known exploitation. EPSS puts it in the 10th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 463d018323851a608eef52a9427b0585005c647f, < 96bef5667b0c4aecb1b850d2343f69b9d684abb9Upgrade to: 96bef5667b0c4aecb1b850d2343f69b9d684abb9Affected: ≥ 463d018323851a608eef52a9427b0585005c647f, < 739b7bf3942da4cde8eedb143d01a16ed865d1d7Upgrade to: 739b7bf3942da4cde8eedb143d01a16ed865d1d7Affected: ≥ 463d018323851a608eef52a9427b0585005c647f, < a41bd1938a9bfe226d444172a7e20e4bd5097960Upgrade to: a41bd1938a9bfe226d444172a7e20e4bd5097960Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS10th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 10th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 8 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Publishedrecord updated

Affected products

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.