[CVE-2026-74401][MODERATE 7.0] dlm: fix add msg handle in send_queue ordered [ Upstream

[CVE-2026-74401][MODERATE 7.0] dlm: fix add msg handle in send_queue ordered [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74401
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: dlm: fix add msg handle in send_queue ordered [ Upstream
Commit: ae9e534e502a0f48c12baf83608c5de0ff0eab11
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ae9e534e502a0f48c12baf83608c5de0ff0eab11
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74401
Analysis date: Sun, 16 Aug 2026 00:44:13 -0400
ActionableScore: 6
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A DLM midcomms race can insert a message handle into `send_queue` before assigning its sequence number, breaking ACK ordering assumptions and causing refcounting errors and use-after-free under heavy DLM message load.

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

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

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-74401	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';CWE-362;*CWE-416;*CWE-672;Other CVSS 'AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.1';DESCR 'A race in DLM midcomms can assign mh seq after the message handle is already inserted into node send_queue, so the queue order may not match the sequence order expected by dlm_receive_ack. Under heavy DLM request load this can break acknowledgement processing and lead to refcounting errors and use-after-free of send buffers. For the CVSS the PR:L is used because reliable triggering normally requires a local user or service that can generate DLM workload on a cluster node, or access as a cluster adjacent peer, but not full administrative privileges on the victim. The issue is network adjacent rather than Internet remote because DLM is normally used on trusted cluster networks. Impact is at least denial of service via crash or corrupted DLM state, and the use-after-free class makes limited or high confidentiality and integrity impact plausible enough for manual review.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	DISK SIMPLEFIX IMPROVEONLY LINUS IO_URING  DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6 DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	YES	NO	checked

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

ActionableScore=6
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 6
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable within cluster context: +2. DLM messages are exchanged over the cluster network, but this is not public Internet remote exposure.
* Memory corruption, weak/indirect corruption candidate: +1. The commit explicitly mentions refcounting issues and use-after-free, but no reclaim, overwrite, callback control, or type confusion primitive is shown.
* Real lifetime corruption: +1. The bug affects ordering of send_queue entries and can produce stale lifetime/refcount handling of send buffers.
* Reliable kernel crash / strong DoS: +1. UAF/refcount corruption in DLM message buffers can realistically destabilize the kernel or DLM subsystem.
* Hard or unreliable race / special timing required: -1. The issue was reproduced only under heavy benchmark load in an experimental DLM branch with io_uring.
* Rare and configuration-dependent subsystem: -1. DLM is mainly used in clustered filesystem deployments and is not a default common desktop/server path.

Paranoid additions:

* Weak LPE concern: +1. Because the bug class is UAF/refcount lifetime corruption in kernel networking/cluster message handling, limited integrity impact cannot be ruled out, but no strong LPE primitive is demonstrated.
* Integrity impact plausible: +1. Refcount misuse and stale send-buffer lifetime may corrupt kernel/DLM state beyond a clean crash, but this remains a manual-review concern rather than a proven exploit path.

## 3. Reachability analysis

The most realistic trigger is a local user or service on a configured DLM cluster node that can generate heavy DLM activity, or a cluster-adjacent peer that can influence DLM message load. It is network-adjacent, not generally Internet-reachable, because DLM is normally deployed only on trusted cluster networks. Namespace/container reachability depends on whether the container or service can access the clustered filesystem or DLM-using workload. The path is not default-enabled on ordinary Linux systems and requires a DLM cluster configuration.

Call-site confidence: medium. The patch shows the lifetime/order fix in `midcomms_new_msg_cb()`, and the commit explains the dependent `dlm_receive_ack()` ordering assumption, but the full receive/free path is not included.

## 4. Severity interpretation

This is stronger than an ordinary Moderate because the commit explicitly identifies refcounting problems and use-after-free, not just a warning or resource leak. Realistic exploitation evidence is limited because the reproducer required heavy benchmark conditions and no attacker-controlled reuse or write primitive is shown. Conservative handling is borderline manual-review Moderate. Paranoid handling is Actionable Moderate because a race-dependent UAF in cluster message lifetime management can plausibly have impact beyond DoS.

## 5. One-sentence report phrase

A DLM midcomms race can insert a message handle into `send_queue` before assigning its sequence number, breaking ACK ordering assumptions and causing refcounting errors and use-after-free under heavy DLM message load.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.

Reason: the patch and commit explicitly mention use-after-free and refcounting issues in a network-adjacent clustered kernel subsystem, even though the demonstrated trigger appears race-dependent and configuration-specific.

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

Patch: dlm: fix add msg handle in send_queue ordered [ Upstream
Commit: ae9e534e502a0f48c12baf83608c5de0ff0eab11
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ae9e534e502a0f48c12baf83608c5de0ff0eab11

Changed files:
  fs/dlm/midcomms.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=ae9e534e502a0f48c12baf83608c5de0ff0eab11

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

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

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:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7.1

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: 4
  Paranoid ActionableScore: 6

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).