Strix
69.2K

CVE-2026-98424

Unknown

Last modified

CVE-2026-98424 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 463d018323851a608eef52a9427b0585005c647f, < 96bef5667b0c4aecb1b850d2343f69b9d684abb9; >= 463d018323851a608eef52a9427b0585005c647f, < 739b7bf3942da4cde8eedb143d01a16ed865d1d7; >= 463d018323851a608eef52a9427b0585005c647f, < a41bd1938a9bfe226d444172a7e20e4bd5097960
LinuxLinux2.6.32

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98424?
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.
How severe is CVE-2026-98424?
Severity scoring for CVE-2026-98424 is pending analysis.
How do I fix CVE-2026-98424?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98424?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST