Skip to main content

Linux Kernel CVE-2026-98359

| EUVDEUVD-2026-93344 HIGH
2026-10-06 Linux GHSA-fhcv-jhv5-h3gg
7.0
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local low-privileged access on RDMA-enabled host
  2. Delivery
    Initiate asynchronous RDMA port speed query during netdev teardown
  3. Exploit
    Win race against NETDEV_UNREGISTER before RTNL check
  4. Execution
    Invoke ethtool callback on stale net_device
  5. Impact
    Kernel use-after-free, memory corruption or panic

Vulnerability Assessment

Exploitation Conditions

Requires: (1) a host with an active RDMA device whose link layer is Ethernet (RoCE) or InfiniBand so that ib_get_eth_speed()/ib_device_get_netdev() is exercised; (2) a net_device that is in the process of unregistering (NETDEV_UNREGISTER and ndo_uninit completed) while its reference is still held; and (3) an asynchronous RDMA port query that races into the stale device's ethtool callback. Limiting factors per CVSS: local access only (AV:L), low privileges needed (PR:L), no user interaction, and HIGH attack complexity (AC:H) because success depends on winning a narrow timing window during device teardown - hosts without RDMA/InfiniBand/RoCE hardware or configuration are not exposed at all.

Impact

This is a race condition in the Linux kernel's RDMA/core subsystem (ib_get_eth_speed) where an asynchronous RDMA port query can invoke a net_device's ethtool callback after NETDEV_UNREGISTER/ndo_uninit have completed, i.e. a use-after-registration/use-after-free class defect. The provided CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N, C:H/I:H/A:H, score 7.0) is internally consistent: it correctly models LOCAL access, LOW privileges, and notably HIGH attack complexity, which captures the narrow race window between the port query and device teardown - this flaw is not trivially triggerable on demand. The real-world risk signals all point the same direction and are low: EPSS is 0.17% (5th percentile), there is no CISA KEV listing, and no public POC is indicated. No SSVC decision data was provided. The high C/I/A impact reflects generic kernel memory-corruption scoring rather than a demonstrated exploit, and the AC:H race requirement plus local PR:L requirement make reliable weaponization difficult. Note a labeling tension: the input Tags mark this 'Information Disclosure,' but the description describes a use-after-free/stale-pointer race on an unregistering netdev, whose most likely practical outcome is a kernel crash (DoS) rather than data leakage - treat the information-disclosure framing with caution. Overall this is a legitimate correctness/stability fix worth patching through normal stable-kernel update cycles, but it is NOT an emergency: high CVSS is driven by worst-case kernel impact assumptions, while every exploitation-probability signal (EPSS, KEV, POC) indicates low real-world urgency.

Exploit ScenarioDerived

A local, low-privileged user on a host with an active RDMA/InfiniBand or RoCE device triggers an asynchronous RDMA port speed query at the exact moment the associated network device is being unregistered (e.g. during interface teardown or driver removal). If the attacker wins the narrow race, ib_get_eth_speed() calls the ethtool callback of a device that has already passed NETDEV_UNREGISTER/ndo_uninit, dereferencing stale state and likely crashing the kernel or corrupting memory. No public exploit identified at time of analysis, and the high attack complexity (race window) makes reliable triggering difficult.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Local users with low privileges can drive the Linux kernel into a race condition in the RDMA/core helper ib_get_eth_speed(), which calls a net_device's ethtool callback after that device has already completed NETDEV_UNREGISTER and ndo_uninit during teardown, corrupting or crashing the kernel. Exposure is narrow: the host must have an active RDMA device bound to an Ethernet (RoCE) or InfiniBand link layer and that device must be unregistering while an asynchronous RDMA port query is in flight, so exploitation requires winning a tight timing window (upstream CVSS 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; the independent assessment keeps the same AV:L/AC:H/PR:L vector but rates confidentiality and integrity as low and availability as high). Vendor-released patches exist for stable branches 6.1.189, 6.6.158, 6.12.112, 6.18.54 and 7.2.8 (plus 7.3-rc4); no public exploit code or confirmed active exploitation is known, and EPSS is only 0.17% (5th percentile).

RemediationAI

Apply the vendor-released kernel patch: upgrade to Linux 6.1.189, 6.6.158, 6.12.112, 6.18.54 or 7.2.8 (mainline fixed in 7.3-rc4), or backport the relevant stable commit (45c60ffc79771bad154f224a05753191cf1b37bc, 520cd057f138ed8dbe8e05f0eae3a8ed4c5d3a5e, 5bd42f74ec3b4f4687fb600f367af0828d513b3c, a219459fbd1b2598e63c81a52847eba6c28b72d2, be4b44c8b47c67a04c08b1a0aba18006b749ae6a or ef9fbe1b93f3b617b96e86d5cd76b3fa44514cb5, listed at https://git.kernel.org/stable/c/be4b44c8b47c67a04c08b1a0aba18006b749ae6a and the other git.kernel.org/stable URLs, with NVD context at https://nvd.nist.gov/vuln/detail/CVE-2026-98359). Because the race requires local low-privileged access to RDMA hardware, a practical interim control is to remove the RDMA binding before the network interface is torn down - for example run 'rdma link delete' / unbind the RDMA device (or unload the ib_core/rdma_ucm and HCA driver modules) prior to 'ip link set <dev> down' or driver unbind during maintenance, which closes the window at the cost of dropping RDMA traffic and requiring a coordinated maintenance sequence. Reducing the frequency of RDMA port-state polling (monitoring agents, ibstat/ibv_devinfo loops, rdma sysfs polling) during interface teardown narrows but does not eliminate the race, and restricting local access to /dev/infiniband, RDMA sysfs entries and the rdma netlink family to trusted users limits who can trigger the asynchronous query - though this conflicts with legitimate non-root RDMA consumers. Since the race occurs only on hosts with RoCE/InfiniBand and an unregistering net_device, systems without RDMA hardware need no compensating action beyond normal kernel update cycles.

Affected VersionsENISA

Linux d41861942fc55c14b6280d9568a0d0112037f065 <ef9fbe1b93f3b617b96e86d5cd76b3fa44514cb5
Linux d41861942fc55c14b6280d9568a0d0112037f065 <a219459fbd1b2598e63c81a52847eba6c28b72d2
Linux d41861942fc55c14b6280d9568a0d0112037f065 <45c60ffc79771bad154f224a05753191cf1b37bc
Linux patch: 7.2.8
Linux patch: 0
Linux 4.14
Linux patch: 7.3-rc4
Linux d41861942fc55c14b6280d9568a0d0112037f065 <520cd057f138ed8dbe8e05f0eae3a8ed4c5d3a5e
Linux patch: 6.18.54
Linux patch: 6.12.112
Linux patch: 6.1.189
Linux d41861942fc55c14b6280d9568a0d0112037f065 <5bd42f74ec3b4f4687fb600f367af0828d513b3c
Linux patch: 6.6.158
Linux d41861942fc55c14b6280d9568a0d0112037f065 <be4b44c8b47c67a04c08b1a0aba18006b749ae6a

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw sits in the Linux kernel RDMA/core stack, specifically the ib_get_eth_speed() path used to report link speed of an RDMA device whose link layer is Ethernet (RoCE) or InfiniBand. ib_device_get_netdev() deliberately returns a reference to a struct net_device even while that device is unregistering, so that association-matching and cleanup code can still find it; the reference only guarantees the memory remains allocated, not that the device is operational. ib_get_eth_speed() violates that contract by treating the returned device operationally: it invokes the netdev's ethtool callback (e.g. get_link_ksettings) under RTNL without first checking the registration state, so an asynchronous RDMA port query can race past NETDEV_UNREGISTER and ndo_uninit and call into driver state that has already been torn down. The fix checks for NETREG_REGISTERED while holding RTNL and returns -ENODEV for a device being unregistered, holds RTNL across both the check and the ethtool call so unregistration cannot start in between, keeps the speed fallback and warning under RTNL so netdev->name is safe to read, and drops the netdev reference before releasing RTNL. No CWE was supplied by the source data, but the root-cause class is a lifetime/state race between device unregistration and asynchronous query handling (a use-after-teardown condition against net_device driver state rather than a classic heap use-after-free, since the netdev memory itself is reference-counted). Affected platform is identified by CPE cpe:2.3:a:linux:linux, i.e. all Linux kernel builds containing the introducing commit and any configured with RDMA/RoCE/InfiniBand support.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 5.8 MEDIUM

Local-only RDMA port query (AV:L), timing race gives AC:H, low privilege suffices (PR:L); most realistic impact is kernel crash (A:H) with limited C/I from stale-pointer reads.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 07, 2026 - 07:22 NVD
7.0 (HIGH)
Patch available
Oct 06, 2026 - 10:02 EUVD
CVE Published
Oct 06, 2026 - 08:46 cve.org
HIGH 7.0
CVE Published
Oct 06, 2026 - 08:46 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

RDMA/core: Reject unregistering netdevs in ib_get_eth_speed

ib_device_get_netdev() intentionally returns a referenced net_device even when it is unregistering, so matching and cleanup callers can still find the association. The reference keeps struct net_device allocated, but does not guarantee that the device remains operational.

ib_get_eth_speed() uses the returned device operationally by invoking its ethtool callback. Although that call is made under RTNL, the function does not verify the registration state first. An asynchronous RDMA port query can therefore call into a netdev after NETDEV_UNREGISTER and ndo_uninit have completed.

Check for NETREG_REGISTERED while holding RTNL and return -ENODEV for a device which is being unregistered. Keeping RTNL across the check and the ethtool operation prevents unregister from starting between them.

Keep the speed fallback and warning under RTNL as well, so the warning can safely read netdev->name. Drop the netdev reference before releasing RTNL once all accesses to the device are complete.

Executive ViewAI

Why It Matters

A high-severity Linux kernel race condition in the RDMA core helper affects servers using RDMA over Converged Ethernet or InfiniBand, where an authenticated local low-privileged user can crash or corrupt the kernel during device teardown. The impact is concentrated on RDMA-dependent high-performance networking, storage, or compute workloads, and no public exploit identified at time of analysis. Leadership should prioritize patching RDMA-enabled Linux fleets because unmitigated kernel crashes could disrupt critical services despite the narrow timing and hardware requirements.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Ubiquitous
Linux kernel is ubiquitous; only RDMA/InfiniBand/RoCE-enabled hosts are exposed
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy