CVE-2026-98311: Linux kernel · wifi: virt_wifi: don't transfer operstate before register
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in f9526054c2b2cace5916b7225603d008834ec011 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f9526054c2b2cace5916b7225603d008834ec011, ee9ea1afd6990def51d52b3a0aecd5cfcc951da0, e8304e25c6dabb8accf38b807969438d0ce84fd7 +5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users and administrators should update to a Linux kernel version that includes the fix commits identified (e.g., commits f9526054c2b2cace5916b7225603d008834ec011 and others). No additional mitigation steps are required beyond applying the official patch.
Description
CVE-2026-98311 is a high-severity vulnerability in the Linux kernel's virt_wifi component. The issue arises because virt_wifi_newlink() calls netif_stacked_transfer_operstate() before the network device is registered, which can lead to a use-after-free condition if registration fails. This occurs when the lower device is dormant and the new network device is queued on an event list while uninitialized. Subsequent cleanup frees the device object, but later event handling accesses the freed memory. The flaw has been fixed by moving the operstate transfer to after the device registration step.
References
- git.kernel.org/stable/c/ee9ea1afd6990def51d52b3a0aecd5cfcc951da0 (opens in a new tab)
- git.kernel.org/stable/c/9ce26201f6dedf3fa02b97da8c67ee6f6c5f7225 (opens in a new tab)
- git.kernel.org/stable/c/f9526054c2b2cace5916b7225603d008834ec011 (opens in a new tab)
- git.kernel.org/stable/c/e8304e25c6dabb8accf38b807969438d0ce84fd7 (opens in a new tab)
- git.kernel.org/stable/c/ca49763c42c1089d654bf11b037980a9ede3772c (opens in a new tab)
- git.kernel.org/stable/c/293c56a66510bb7de073a1aba388e38abddff1fb (opens in a new tab)
- git.kernel.org/stable/c/b808a9af5fd21f9c68b0d024eda7535b5dce6a4e (opens in a new tab)
- git.kernel.org/stable/c/e5c8d7acd31b27057ea42cd405d0b3ece097bc89 (opens in a new tab)