[CVE-2026-74395][MODERATE 7.0] RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference [ Upstream

[CVE-2026-74395][MODERATE 7.0] RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74395
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference [ Upstream
Commit: 6e15b770461eeaa0ff73934922cb670a6a9db04e
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6e15b770461eeaa0ff73934922cb670a6a9db04e
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74395
Analysis date: Sat, 15 Aug 2026 20:05:03 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-74395 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74395

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-74395	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';**CWE-476;CWE-665;CWE-703;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'RDMA mlx5 DEVX subscribe event error handling can dereference a NULL ev_file pointer because event_sub is added to sub_list before fields used by the shared unwind path are initialized. A local process with access to the mlx5 uverbs DEVX interface can trigger this by making eventfd_ctx_fdget fail during MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT, causing cleanup to call uverbs_uobject_put on an unset ev_file and to use an unset xa_key_level1. For the CVSS the PR:L is used because reliable triggering requires local code execution and access to the RDMA uverbs device, but not full administrator privileges in deployments where RDMA device nodes are delegated to users or containers. The issue is not directly network reachable. Impact is at least denial of service via kernel crash. Because the unwind path can also deallocate the wrong XA subscription entry, limited confidentiality or integrity impact is a conservative paranoid assumption and should be manually reviewed.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)	YES	NULLPTR ERRORPATH NETWORK HARDWARE LINUS  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=3

1. ActionableScore
* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

2. Signal breakdown
* Local unprivileged trigger: +1. A local process with access to the mlx5 RDMA uverbs DEVX interface can reach MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT.
* Memory corruption, weak/indirect corruption candidate: +1. The NULL ev_file dereference is mainly a crash primitive, but the unset xa_key_level1 can also drive wrong XA subscription cleanup in the unwind path.
* Real lifetime / cleanup ordering issue: +1. event_sub is linked into sub_list before fields needed by cleanup are initialized, creating a partially initialized object lifetime hazard.
* Reliable kernel crash / strong DoS: +1. The commit explicitly describes a NULL dereference through uverbs_uobject_put after eventfd_ctx_fdget failure.
* Weak LPE concern, paranoid only: +1. Wrong XA deallocation is not a proven exploit primitive, but it is enough to justify manual review as a possible object bookkeeping corruption sink.
* Rare and configuration dependent subsystem: -1. Exposure requires mlx5 RDMA hardware, DEVX/uverbs availability, and access to the RDMA device node.
* Constrained or metadata-only corruption uncertainty: -1 conservative. No attacker-controlled overwrite, reclaim, callback hijack, or arbitrary write is shown.

3. Reachability analysis
The bug is locally reachable through RDMA uverbs DEVX subscription setup, not through packets from the network. Triggering requires local code execution and access to the mlx5 uverbs device. This is usually PR:L rather than PR:H when RDMA device nodes are delegated to users, containers, HPC jobs, or service accounts. In locked-down systems without user RDMA access, practical reachability is much lower. The path is not a broad default kernel path and depends on specific mlx5 RDMA deployment.

Call-site confidence: high, because the changed function and unwind path are included in the supplied patch context.

4. Severity interpretation
This behaves above ordinary Moderate because it is a local kernel crash in a privileged RDMA object-management path and also has a secondary wrong-XA-cleanup concern. Realistic demonstrated impact is DoS via NULL dereference. Theoretical escalation is weak and not demonstrated, because the patch does not show attacker-controlled reclaim, write-after-free, callback control, or arbitrary write. The best practical bucket is Actionable Moderate at minimum, not a Strong Important candidate.

5. One-sentence report phrase
A local process with access to mlx5 RDMA DEVX can trigger an unwind path where a partially initialized event_sub is cleaned up, causing a NULL pointer dereference and possible XA subscription bookkeeping corruption.

6. Manual review recommendation
MANUAL CHECK REQUIRED. The primary impact is a local kernel crash, but the unset xa_key_level1 cleanup path may corrupt subscription bookkeeping, so this should not be auto-closed without RDMA/uverbs-specific review.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference [ Upstream
Commit: 6e15b770461eeaa0ff73934922cb670a6a9db04e
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6e15b770461eeaa0ff73934922cb670a6a9db04e

Changed files:
  drivers/infiniband/hw/mlx5/devx.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6e15b770461eeaa0ff73934922cb670a6a9db04e

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-74395 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74395

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 5.8

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 3
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).