Cloudanix VulnDB

CVE-2026-98311

High · 7.8

CVSS

7.8

EPSS

0.1%

Published

Oct 6, 2026

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A flaw in how Linux handles certain virtual network setups can let local users crash the system or potentially gain higher privileges.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Moderate
Impact
Full Compromise
Component
OS kernel
Class
Use After Free
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Use-after-free in the Linux kernel virt_wifi driver caused by calling netif_stacked_transfer_operstate before register_netdevice, allowing a freed netdev list entry to be accessed later via linkwatch_fire_event when registration fails.

Why it matters to the business

Local attackers on affected Linux systems can trigger kernel crashes or memory corruption leading to denial of service or potential privilege escalation, impacting system availability and security posture on wireless virtualization setups.

How an attack unfolds

An attacker with local access creates a virt_wifi interface using an invalid name such as one containing a slash, causing netif_stacked_transfer_operstate to queue the uninitialized device; subsequent registration failure frees the object while linkwatch later dereferences the stale list entry, resulting in use-after-free.

How to fix it

Apply the upstream kernel patch that moves netif_stacked_transfer_operstate after netdev_upper_dev_link in virt_wifi_newlink; rebuild and deploy updated kernels containing the fix for all affected distributions.

How to confirm the fix worked

Inspect kernel source for virt_wifi_newlink to confirm netif_stacked_transfer_operstate is called after netdev_upper_dev_link; verify running kernel version includes the resolution commit and test interface creation with invalid names does not panic.

Typical attack path

  1. Obtain local user access on a Linux system with virt_wifi enabled
  2. Invoke netlink or ioctl to create a virt_wifi interface with an invalid device name
  3. Trigger registration failure path after the premature operstate transfer
  4. Force linkwatch event processing to access the freed object

How to detect it

Review kernel logs for use-after-free warnings or panics involving linkwatch, lweventlist, or virt_wifi_newlink; correlate with audit logs showing netlink interface creation attempts with malformed names.

What your security team should do

  • Prioritize kernel updates on all systems exposing virt_wifi or wireless virtualization
  • Restrict unprivileged local users from creating network interfaces via policy or namespaces until patched
  • Monitor for kernel oops or panic logs related to netdevice list handling
  • Review and limit use of virt_wifi in production environments

The record

In the Linux kernel, the following vulnerability has been resolved: wifi: virt_wifi: don't transfer operstate before register virt_wifi_newlink() calls netif_stacked_transfer_operstate() before register_netdevice(). If the lower device is dormant, that queues the new netdev on lweventlist while it is still uninitialized. If registration fails after that, for example because of an invalid name such as "bad/name", free_netdev() immediately frees the object. A later linkwatch_fire_event() then use-after-frees the list entry. Move the transfer to after netdev_upper_dev_link(), as macvlan and ipvlan already do.

Affected packages

Ecosystem Package Introduced Fixed