Skip to main content

Linux Kernel EUVDEUVD-2026-59544

| CVE-2026-74397 HIGH
2026-08-15 Linux GHSA-85rj-hfqq-77v3
High
Disputed · 7.8 Vendor: Linux
View

Attack ChainAIDerived

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

  1. Access
    Gain local access with RDMA group membership
  2. Delivery
    Load or target mlx5_ib driver on ConnectX hardware
  3. Exploit
    Repeatedly trigger transport domain allocation with engineered mlx5_ib_enable_lb() failure
  4. Execution
    Accumulate leaked TD kernel objects
  5. Persist
    Exhaust kernel slab memory
  6. Impact
    Trigger denial of service or probe leaked TD for kernel memory disclosure

Vulnerability Assessment

Exploitation Conditions

Exploitation requires: (1) local authenticated access to the target system (CVSS PR:L confirmed); (2) the system must have a Mellanox/NVIDIA ConnectX adapter present and the mlx5_ib kernel module loaded (hardware-specific precondition); (3) the attacker must be able to invoke IB/RDMA operations - typically requiring membership in the 'rdma' group or root-equivalent access to InfiniBand device nodes. The leak is triggered only when mlx5_ib_enable_lb() returns an error after a successful TD allocation, which may require engineering specific failure conditions (e.g., device resource exhaustion). The mutex initialization race is limited to the driver initialization window. Exploitation is constrained by: local-only attack vector, hardware dependency (mlx5 ConnectX required), RDMA subsystem access controls, and the need to reliably trigger a specific error-path condition. Remote exploitation is not applicable.

Impact

The NVD-assigned CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) appears inflated relative to the described defect. A transport domain leak is a resource management flaw; C:H and I:H are difficult to justify from the description alone unless the leaked TD can be dereferenced or reused in a way that exposes or corrupts kernel memory - which the description does not confirm. The 'Information Disclosure' tag suggests some kernel memory exposure is possible, but its mechanism is not specified. EPSS at 0.17% (7th percentile) strongly corroborates low real-world exploitation interest. This CVE is not listed in CISA KEV and no public proof-of-concept is identified. The primary realistic risk is local denial of service through repeated triggering of the error path to exhaust kernel TD objects, and potentially a kernel panic from the uninitialised mutex if hit before initialization completes. CVSS AV:L/PR:L correctly gates the risk behind local access on hardware-specific systems. Net assessment: low practical priority outside of HPC or RDMA-heavy data center environments; patch during the next maintenance window rather than emergency.

Exploit ScenarioDerived

A local user with at least standard user privileges on a Linux system equipped with a Mellanox/NVIDIA ConnectX adapter could repeatedly invoke RDMA operations that trigger the mlx5 transport domain allocation path, engineering conditions under which mlx5_ib_enable_lb() returns an error (e.g., by exhausting loopback table entries or via a race). Each failed attempt leaks one TD object from kernel memory. Iterating this across thousands of attempts could exhaust kernel slab memory, leading to a system-wide denial of service or, if the leaked TD object is reachable, a potential kernel memory disclosure. No public proof-of-concept is identified at time of analysis.

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 – Aug 17, 2026

Resource leak and premature mutex use in the Linux kernel's mlx5 InfiniBand driver (IB/mlx5) expose systems with Mellanox/NVIDIA ConnectX hardware to local privilege escalation, denial of service, and potential information disclosure. When mlx5_ib_alloc_transport_domain() successfully allocates a transport domain (TD) but mlx5_ib_enable_lb() subsequently fails, the TD object is never freed, leaking kernel memory. Compounding this, the loopback mutex (dev->lb.mutex) was initialized too late - after code paths that could use it - creating a window for undefined kernel behavior. No public exploit exists and EPSS sits at 0.17% (7th percentile), placing real-world risk well below the CVSS 7.8 headline score.

RemediationAI

The upstream fix is available across multiple stable branches via the Linux kernel stable tree. Upgrade to one of the patched versions: 6.6.145, 6.12.97, 6.18.40, 7.1.5, or 7.2-rc1, referencing fix commits at https://git.kernel.org/stable/c/2c3b2667dad69d56774b79db763acb3a1bee0fc0, https://git.kernel.org/stable/c/37fc3cc0f924fd8d0f0cf87b92672dec75a32e57, https://git.kernel.org/stable/c/65e344925fa30abf50c8de8c150b397715fa2066, https://git.kernel.org/stable/c/f88e12c95fc19f719e06ca1e9eb20fdad68ef61a, and https://git.kernel.org/stable/c/e79389115b9d27287ff6230a9750675106ed7668. If immediate patching is not feasible and the deployment does not require InfiniBand loopback functionality, unloading or blacklisting the mlx5_ib kernel module (echo 'blacklist mlx5_ib' >> /etc/modprobe.d/blacklist.conf) eliminates the vulnerable code path entirely - trade-off is loss of RDMA/InfiniBand functionality on ConnectX adapters. Restricting access to RDMA character devices (/dev/infiniband/) to trusted users via udev rules reduces the attack surface but does not eliminate the kernel-side defect.

Affected VersionsENISA

Linux patch: 6.6.145
Linux 146d2f1af3245a10b13eef263687e54f4e253d1d <65e344925fa30abf50c8de8c150b397715fa2066
Linux 146d2f1af3245a10b13eef263687e54f4e253d1d <2c3b2667dad69d56774b79db763acb3a1bee0fc0
Linux patch: 7.2-rc1
Linux 146d2f1af3245a10b13eef263687e54f4e253d1d <37fc3cc0f924fd8d0f0cf87b92672dec75a32e57
Linux 4.5
Linux 146d2f1af3245a10b13eef263687e54f4e253d1d <f88e12c95fc19f719e06ca1e9eb20fdad68ef61a
Linux patch: 6.12.97
Linux patch: 7.1.5
Linux 146d2f1af3245a10b13eef263687e54f4e253d1d <e79389115b9d27287ff6230a9750675106ed7668
Linux patch: 6.18.40
Linux patch: 0

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 mlx5 InfiniBand driver (IB/mlx5) manages RDMA transport domains, which are kernel objects that namespace memory protection in Mellanox/NVIDIA ConnectX adapters operating in InfiniBand or RoCE mode. Transport domains are allocated via mlx5_ib_alloc_transport_domain() and then refined by mlx5_ib_enable_lb() to configure loopback capability. The two-phase initialization contains a classic TOCTOU-style resource management flaw: if phase two fails, the phase-one allocation is not rolled back. The CWE is recorded as N/A by NVD, but this maps to CWE-772 (Missing Release of Resource after Effective Lifetime) for the TD leak and CWE-908 (Use of Uninitialized Resource) for the mutex initialization ordering defect. The affected CPE is cpe:2.3:a:linux:linux and the vulnerability was introduced at commit 146d2f1af3245a10b13eef263687e54f4e253d1d (Linux 4.5). Only kernels built with mlx5 InfiniBand support and running on hardware with Mellanox/NVIDIA ConnectX adapters are in scope.

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

Sources disagree (Low–High)
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 5.3 MEDIUM

Local-only, hardware-specific (mlx5 required), AC:H for engineered error-path; A:H for resource exhaustion; C:L for possible TD memory exposure; I:N unconfirmed.

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

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

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

4
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:19 EUVD
CVE Published
Aug 15, 2026 - 05:59 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 05:59 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier

mlx5_ib_alloc_transport_domain() allocates a transport domain and then may fail in mlx5_ib_enable_lb(). In that case, the allocated TD is leaked.

Fix this by deallocating the TD when mlx5_ib_enable_lb() returns an error. Also return 0 explicitly in the no-loopback-capability success branch, and move dev->lb.mutex initialization to mlx5_ib_stage_init_init().

Executive ViewAI

Why It Matters

CVE-2026-74397 affects the Linux kernel's mlx5 InfiniBand driver on systems with Mellanox/NVIDIA ConnectX hardware, potentially enabling local privilege escalation and denial of service. While the vulnerability carries CVSS 7.8 (HIGH), real-world exploitation risk is minimal (0.2% EPSS) with no public exploit identified at time of analysis; organizations should prioritize patching infrastructure systems, particularly in data center and HPC environments where insider threats or lateral movement through networked systems present the primary risk.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
common in HPC and data center RDMA deployments, not general Linux
Data Quality
5 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
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

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: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

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