Skip to main content

Linux Kernel EUVDEUVD-2026-86149

| CVE-2026-93277 HIGH
2026-09-24 Linux GHSA-4gwr-wcr3-5gpm
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

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

  1. Access
    Gain local access to RDMA uverbs device
  2. Delivery
    Issue destroy verb on driver resource
  3. Exploit
    Force udata copy-out failure post-teardown
  4. Execution
    Re-run destroy on freed resource (UAF/double-free)
  5. Impact
    Corrupt kernel memory for privilege escalation

Vulnerability Assessment

Exploitation Conditions

Requires a local user with access to the kernel RDMA/InfiniBand userspace-verbs interface (e.g., /dev/infiniband/uverbsN) on a system running the bnxt_re driver, i.e., a Broadcom NetXtreme-E adapter operating in RoCE/RDMA mode - this is not a default configuration on general-purpose hosts. Triggering requires forcing the uverbs udata copy to userspace to fail after resource teardown so the destroy callback re-runs against freed driver state; the create-AH variant additionally leaks the HW object. Limiting factors: PR:L (needs an existing local account with RDMA device permissions), AV:L (no remote/network reach), no user interaction, and hardware/driver dependency on Broadcom RDMA NICs.

Impact

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) describes a classic local privilege-escalation-class memory-safety flaw in the kernel: an authenticated local user with access to the RDMA userspace-verbs (uverbs) interface can trigger repeated execution of a destroy callback against already-freed driver resources - a use-after-free / double-free (the listed CWE is N/A, but the described 'run again after resource freed' behavior is CWE-416/CWE-415, not the 'Information Disclosure' the tag claims). No EPSS score, KEV entry, or public POC is present in the input, so exploitation is: no public exploit identified at time of analysis. Real-world priority is moderate and bounded: this is a genuine kernel memory-corruption bug (patched upstream via two git.kernel.org stable commits), but it is reachable only on systems that actually load the bnxt_re driver (Broadcom NetXtreme-E RoCE NICs) with RDMA userspace configured, and it requires a pre-existing local foothold (PR:L). There is no signal of active or automatable mass exploitation, so this is a patch-in-normal-cycle item for RDMA-enabled hosts rather than an emergency. Note the CVSS is local (AV:L) and consistent with the description; no network-vector conflict exists.

Exploit ScenarioDerived

A local unprivileged (but RDMA-capable) user on a host with a Broadcom bnxt_re RoCE adapter issues a destroy verb (e.g., destroy AH/QP/CQ) and arranges for the userspace udata copy-out to fail after the driver has torn down the resource; uverbs preserves the uobject and re-invokes the destroy callback, operating on freed memory. Repeated triggering yields a use-after-free/double-free that can be groomed toward kernel memory corruption and privilege escalation. No public POC is referenced in the provided data.

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

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

Alert me

AnalysisAIv1 – Sep 25, 2026

Local privilege escalation-class memory-safety flaw in the Linux kernel's RDMA/bnxt_re driver allows an authenticated local user with access to the RDMA userspace-verbs interface (/dev/infiniband/uverbsN) to trigger use-after-free or double-free conditions by forcing udata copy failures after resource teardown, causing destroy callbacks to run again against freed driver state; a create-AH path can also leak a hardware object. The CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), and exploitation requires a Broadcom NetXtreme-E adapter running bnxt_re in RoCE/RDMA mode, which is not a default configuration on general-purpose hosts. No public exploit was identified at time of analysis.

RemediationAI

Vendor-released patch: update to Linux 7.2.6 or 7.3-rc1 (or a later stable release) that contains the fixes c5643ea4f040acc2f4d1e88f49bd0be51110ff2f and d38c835925d4a3bfdf0a85ff2829ee90c709c561; consult https://git.kernel.org/stable/c/c5643ea4f040acc2f4d1e88f49bd0be51110ff2f and https://git.kernel.org/stable/c/d38c835925d4a3bfdf0a85ff2829ee90c709c561 and apply the matching distribution kernel update. If immediate patching is not possible, restrict access to /dev/infiniband/uverbsN so only fully trusted local users can issue RDMA uverbs commands, and for hosts that do not require Broadcom RoCE/RDMA, unload or blacklist the bnxt_re driver (for example, blacklist bnxt_re or remove the module) to eliminate the vulnerable code path; both mitigations trade off by disabling or limiting legitimate RDMA/RoCE functionality. There is no KEV entry or public exploit code identified in the provided data, so exposure is currently dependent on local access to the RDMA interface and the presence of Broadcom NetXtreme-E hardware.

Affected VersionsENISA

Linux patch: 0
Linux bed686d8dcd4fbcaa18cf67468caaf8772acfc7a <d38c835925d4a3bfdf0a85ff2829ee90c709c561
Linux 7.1
Linux patch: 7.2.6
Linux patch: 7.3-rc1
Linux bed686d8dcd4fbcaa18cf67468caaf8772acfc7a <c5643ea4f040acc2f4d1e88f49bd0be51110ff2f

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 bnxt_re driver implements RDMA support for Broadcom NetXtreme-E adapters, including RoCE, and exposes operations through the kernel RDMA userspace-verbs (uverbs) interface such as /dev/infiniband/uverbsN. In the affected destroy callbacks, udata output was zeroed after driver resources were torn down; if the copy to userspace failed, uverbs retained the uobject and allowed the destroy callback to be invoked again even though the driver resource had already been freed, yielding use-after-free/double-free behavior. The fix calls ib_no_udata_io() before teardown so udata failures are detected while the resource is intact and returns success only after teardown, and moves ib_respond_empty_udata() to the start of create and modify flows to avoid leaking the HW object in _rdma_create_ah(). Although the source tag says Information Disclosure, the described 'run again after resource freed' behavior is consistent with CWE-416/CWE-415 rather than an information-disclosure class. CPE data identifies Linux kernel (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*), and the CVSS vector requires local access with PR:L, not remote exploitation.

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.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local RDMA-verbs user (PR:L) triggers a use-after-free/double-free with no interaction; kernel memory corruption plausibly yields full C/I/A impact, matching the vendor 7.8.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE HIGH
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

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

Lifecycle Timeline

3
CVSS changed
Sep 25, 2026 - 05:23 NVD
7.8 (HIGH)
CVE Published
Sep 24, 2026 - 15:52 cve.org
HIGH 7.8
CVE Published
Sep 24, 2026 - 15:52 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

RDMA/bnxt_re: Validate udata before executing commands

The destroy callbacks currently zero the udata output after tearing down driver resources. If the userspace access fails, uverbs preserves the uobject and allows the destroy callback to run again, even though the driver resource has already been freed.

Call ib_no_udata_io() before teardown so udata failures are detected while the resource is still intact, then return success after teardown completes.

As part of this change, move ib_respond_empty_udata() to the start of the create and modify flows. While this is not strictly required for general create flows, as the core layer unwinds uobjects on failure, it is necessary for create AH. In _rdma_create_ah(), the HW object is otherwise leaked.

Executive ViewAI

Why It Matters

A memory-safety flaw in the Linux kernel's Broadcom bnxt_re RDMA driver (CVE-2026-93277) lets an already-authenticated local user escalate to kernel-level privileges on hosts using Broadcom NetXtreme-E adapters in RoCE/RDMA mode. Because the vulnerable configuration is confined to specialized RDMA-enabled servers rather than general-purpose systems, exposure is limited to clusters and workloads running high-speed networking for storage, HPC, or AI traffic. Leadership should care because a successful escalation on such a node can compromise the host kernel and any tenant or data plane workload it supports, though no public exploit code or active exploitation has been reported.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: unload or blacklist the bnxt_re module where RDMA/RoCE is not required; restrict /dev/infiniband/uverbs* to privileged, essential service accounts via file permissions and device cgroup or SELinux policy; limit local shell access on affected nodes; and monitor kernel logs for driver crash signatures indicating use-after-free or double-free activity.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche bnxt_re RDMA driver; needs Broadcom RoCE NIC and RDMA userspace
Data Quality
3 sources
Confidence: Low

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.1%
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

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

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