Skip to main content
Vulnerability Database/CVE-2026-98359

CVE-2026-98359: Linux Kernel RDMA Use-After-Free Vulnerability

CVE-2026-98359 is a use-after-free flaw in Linux kernel RDMA core that occurs when querying network device speed during unregistration. This article covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98359 Overview

CVE-2026-98359 is a Linux kernel vulnerability in the RDMA (Remote Direct Memory Access) core subsystem. The flaw affects ib_get_eth_speed(), which operates on a referenced net_device returned by ib_device_get_netdev() without verifying the netdev's registration state. An asynchronous RDMA port query can invoke an ethtool callback on a netdev after NETDEV_UNREGISTER and ndo_uninit have completed. The resulting access to an unregistered network device can corrupt kernel memory and compromise system integrity.

Critical Impact

Local attackers with low privileges can trigger operations on a partially torn-down netdev, enabling potential kernel memory corruption with impact to confidentiality, integrity, and availability.

Affected Products

  • Linux kernel RDMA/core subsystem (drivers/infiniband/core)
  • Kernel builds containing ib_get_eth_speed() prior to the referenced stable commits
  • Linux distributions shipping affected stable and longterm kernels

Discovery Timeline

  • 2026-10-06 - CVE-2026-98359 published to NVD
  • 2026-10-07 - Last updated in NVD database

Technical Details for CVE-2026-98359

Vulnerability Analysis

The RDMA core helper ib_device_get_netdev() returns a referenced net_device pointer even when the device is unregistering. This design allows matching and cleanup callers to find the association while the netdev is being removed. The returned reference keeps the struct net_device allocation alive but does not guarantee the device remains operational.

ib_get_eth_speed() uses the returned netdev operationally by invoking its ethtool callback to retrieve link settings. The function performs this call under RTNL (Routing Netlink lock) but does not check the registration state before dispatch. As a result, an asynchronous RDMA port query can reach an ethtool handler on a device that has already completed NETDEV_UNREGISTER notification and ndo_uninit cleanup.

Root Cause

The root cause is a missing registration-state check between acquiring the netdev reference and performing operational calls on it. Reference counting prevents the memory from being freed, but driver-specific state and ethtool operations become invalid after ndo_uninit. Invoking an ethtool callback on such a netdev results in a use-after-teardown condition in driver state.

Attack Vector

Exploitation requires local access with low privileges, as reflected by the CVSS vector AV:L/AC:H/PR:L. The attacker must induce a race between an RDMA port query on an Ethernet-backed InfiniBand device and the unregistration of the underlying netdev. High attack complexity reflects the timing precision required to interleave the two operations.

The fix adds a NETREG_REGISTERED check while holding RTNL and returns -ENODEV for a device being unregistered. RTNL is held across both the registration check and the ethtool call, which prevents unregister from starting between them. The speed fallback and warning path are also kept under RTNL so the warning can safely read netdev->name, and the netdev reference is dropped only after all accesses complete. Fix commits include 45c60ffc7977, 520cd057f138, 5bd42f74ec3b, a219459fbd1b, be4b44c8b47c, and ef9fbe1b93f3.

Detection Methods for CVE-2026-98359

Indicators of Compromise

  • Kernel oops or warning messages originating in ib_get_eth_speed or RDMA port query paths
  • Unexpected -ENODEV returns from RDMA port queries during netdev teardown events
  • KASAN reports flagging use-after-free or invalid access within InfiniBand ethtool call paths

Detection Strategies

  • Monitor kernel logs for warnings or stack traces involving ib_device_get_netdev, ib_get_eth_speed, or ethtool get_link_ksettings callbacks
  • Correlate RDMA port query events with netdev unregister notifications on hosts running RoCE or iWARP
  • Run KASAN or KMSAN-enabled test kernels in staging to surface latent race conditions on RDMA-capable systems

Monitoring Recommendations

  • Audit workloads using RDMA verbs with Ethernet-backed providers such as mlx5, irdma, bnxt_re, or qedr
  • Track kernel version inventory across hosts to confirm patch coverage on stable branches
  • Alert on repeated RDMA subsystem warnings coinciding with network interface up/down transitions

How to Mitigate CVE-2026-98359

Immediate Actions Required

  • Update to Linux kernel versions containing the fix commits listed in the kernel.org stable tree
  • Prioritize patching on hosts running RDMA workloads over Ethernet (RoCE, iWARP) or those exposing InfiniBand verbs to local users
  • Restrict local user access to RDMA device files such as /dev/infiniband/* where feasible

Patch Information

The upstream fix adds a NETREG_REGISTERED check under RTNL and returns -ENODEV when the netdev is unregistering. Review the stable commit references for backport details: 45c60ffc7977, 520cd057f138, 5bd42f74ec3b, a219459fbd1b, be4b44c8b47c, and ef9fbe1b93f3. Apply vendor-provided kernel updates once available from your distribution.

Workarounds

  • Avoid dynamic unregistration of Ethernet interfaces that back active RDMA devices while workloads are running
  • Where RDMA is not required, unload affected modules such as ib_core, mlx5_ib, or rdma_rxe to eliminate the vulnerable code path
  • Apply strict permissions on /dev/infiniband/ entries to limit local attack surface
bash
# Restrict access to RDMA verbs device files
chmod 0600 /dev/infiniband/uverbs*
chown root:root /dev/infiniband/uverbs*

# Optionally blacklist RDMA modules on systems not using RDMA
echo "blacklist ib_core" | sudo tee /etc/modprobe.d/disable-rdma.conf
echo "blacklist rdma_rxe" | sudo tee -a /etc/modprobe.d/disable-rdma.conf

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.