CVE-2026-74395

RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference

N/A
Published: August 15, 2026 at 05:59 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT() links event_sub into sub_list before initializing the fields used by the shared error path. If eventfd_ctx_fdget() then fails, the unwind path dereferences event_sub->ev_file in uverbs_uobject_put() and calls subscribe_event_xa_dealloc() with an unset xa_key_level1. subscribe_event_xa_alloc() creates the XA entry exactly once for a given key_level1, on the first occurrence of that key. The unwind path must therefore call subscribe_event_xa_dealloc() exactly once for it as well. Enforce that by adding devx_key_in_sub_list() and calling subscribe_event_xa_dealloc() only when the last matching pending entry is being cleaned up.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.3 ≤ v < 5.10.2615.3 ≤ v < 5.15.2125.3 ≤ v < 6.1.1785.3 ≤ v < 6.12.975.3 ≤ v < 6.18.405.3 ≤ v < 6.6.1455.3 ≤ v < 7.1.55.3 ≤ v < 7.25.37597385371425febdaa8c6a1da3625d4ffff16f5
Vendor states this is fixed in 1025dc2f7ba29b04b8687790fa91f9cd1a53141e (fixed)
Vendor states this is fixed in 43f8f7946814c8e5f464518246fdbc69b6e32326 (fixed)
Vendor states this is fixed in 5100febf8e9d6c8c5ba8dc6534c6a5e3376e5989 (fixed)
Vendor states this is fixed in 6e15b770461eeaa0ff73934922cb670a6a9db04e (fixed)
Vendor states this is fixed in 78b9589fda266c71f0f9d0c858d4fa7381a890a5 (fixed)
Vendor states this is fixed in 7921821fc2b19c01588311f6e7468ae5b68b1f61 (fixed)
Vendor states this is fixed in 9be9aca28424228586fe9211c373ebdb826ebb6c (fixed)
Vendor states this is fixed in f345e744b6b087188cde2377da5cbe9713b61353 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card