CVE-2026-98424Hinoki check available

Namespace-state corruption via failed wiphy rename

Published Oct 14, 2026 · Updated Oct 14, 2026

Namespace-state corruption in Linux cfg80211 allows local users to leave wireless devices inconsistent during namespace moves. In net/wireless/core.c, cfg80211_switch_netns() changes the wiphy namespace before device_rename() moves its sysfs representation, but does not undo the change when renaming fails. Reaching the flaw requires a wireless-device namespace move and an allocation failure; the disclosed consequence is inconsistent namespace state and a kernel warning, not demonstrated code execution.

CVSS severityUnavailable
Unscored
EPSS probability0.21%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Namespace-state corruption in Linux cfg80211 allows local users to leave wireless devices inconsistent during namespace moves. In net/wireless/core.c, cfg80211_switch_netns() changes the wiphy namespace before device_rename() moves its sysfs representation, but does not undo the change when renaming fails. Reaching the flaw requires a wireless-device namespace move and an allocation failure; the disclosed consequence is inconsistent namespace state and a kernel warning, not demonstrated code execution.

The record

CVE
CVE-2026-98424
Published
Oct 14, 2026
Updated
Oct 14, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Oct 14, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 14, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.6.32
  2. Affected versionversion=463d018323851a608eef52a9427b0585005c647f <739b7bf3942da4cde8eedb143d01a16ed865d1d7
  3. Affected versionversion=463d018323851a608eef52a9427b0585005c647f <96bef5667b0c4aecb1b850d2343f69b9d684abb9
  4. Affected versionversion=463d018323851a608eef52a9427b0585005c647f <a41bd1938a9bfe226d444172a7e20e4bd5097960

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=2.6.32; version=463d018323851a608eef52a9427b0585005c647f <739b7bf3942da4cde8eedb143d01a16ed865d1d7; version=463d018323851a608eef52a9427b0585005c647f <96bef5667b0c4aecb1b850d2343f69b9d684abb9; version=463d018323851a608eef52a9427b0585005c647f <a41bd1938a9bfe226d444172a7e20e4bd5097960

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started