[CVE-2026-72344][MODERATE REGULAR] net/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72344
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable [ Upstream
Commit: 5a95aa0198af75047d98fb72950642c89dab770f
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a95aa0198af75047d98fb72950642c89dab770f
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72344
Analysis date: Sat, 15 Aug 2026 22:23:22 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline manual review recommended / ordinary Moderate if confirmed admin-only DoS
Manual review required: YES

Summary:
A negative LAG sequence error in mlx5e TC cleanup can be used as an index into the peer flow list during eswitch or representor teardown, causing out-of-bounds list access and a kernel crash, with practical triggering usually requiring local device-management privileges.

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

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

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 REGULAR
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-72344	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	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-129;CWE-125;*CWE-787;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'mlx5e_tc_clean_fdb_peer_flows() can use a negative LAG sequence value as an index when mlx5_lag_get_dev_seq() fails for a peer that is not in LAG or when no device is marked as master. This can make the cleanup path access memory outside the expected peer flow array during eswitch offload or representor cleanup, causing a kernel crash. For the CVSS the PR:L is used for the paranoid score because delegated CAP_NET_ADMIN, reduced capability root, or service control over mlx5 LAG and eswitch operations can be enough in practical deployments. The issue is not directly network reachable and is triggered by local device or driver control plane operations rather than packet traffic. Impact is at least denial of service via kernel crash and in the worst case may allow limited confidentiality or integrity impact because the failed lookup is used as an array index before list traversal.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended / ordinary Moderate if confirmed admin-only DoS (with actual score 3)  SKIP CVE-2026-72344 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE DANGER NETWORK KERNEL_PANIC_PLUS_UAF HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=3
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 3
* Final recommended bucket: **Borderline manual review recommended / ordinary Moderate if confirmed admin-only DoS**::

## 2. Signal breakdown

Conservative signals:

* Weak/indirect corruption candidate: +1. `mlx5_lag_get_dev_seq()` can return a negative error value, and that value was used as an index into `esw->offloads.peer_flows[i]`.
* Reliable kernel crash / strong DoS: +1. The commit includes a concrete crash trace in `mlx5e_tc_del_fdb_peers_flow()`.
* Privileged kernel/device-management corruption path: +1. The bug is in mlx5 eswitch / LAG / representor cleanup, a trusted driver-management path.
* Requires admin/root/CAP_NET_ADMIN/device control in typical deployments: -2. Reliable triggering normally requires control over mlx5 LAG, eswitch offloads, representor teardown, driver unload, or PCI/device removal.
* Availability impact realistic: +1. The observed failure is a kernel crash in a cleanup path.

Paranoid additional interpretation:

* Weak LPE concern: +1. The failed lookup becomes an array index before list traversal, so this is more than a pure NULL dereference. However, no controlled overwrite, reclaim, type confusion, or arbitrary write primitive is shown.

No remote/network-triggerable signal is awarded. Packet traffic alone is not the trigger path.

## 3. Reachability analysis

The realistic trigger is local control-plane activity involving mlx5 LAG or eswitch offload teardown. Typical examples are device removal, driver cleanup, representor unload, devlink-style management, or LAG state changes.

In normal deployments this requires administrator-level privileges or a service with network-device management rights. In containerized or delegated environments, reduced-capability root or a service account with CAP_NET_ADMIN-like control could reduce the practical privilege barrier, which is why the paranoid score treats this as more actionable.

The path is not directly network reachable. It is hardware and configuration dependent on Mellanox mlx5 devices with relevant LAG/eswitch/offload state.

Call-site confidence: high. The patch shows the direct bad index site, and the commit provides the cleanup call trace leading to the crash.

## 4. Severity interpretation

This behaves mainly like an ordinary to borderline Moderate kernel driver DoS. The concrete demonstrated impact is a kernel crash caused by bad memory access during cleanup.

Theoretical memory-corruption concern exists because a negative error value is used as an array index before list traversal. Realistic privilege escalation is not demonstrated by the patch, and there is no shown attacker-controlled payload, reclaim primitive, arbitrary write, or type confusion. Therefore this should not be treated as an Important-class issue by default, but it should not be auto-closed without checking the OOB access consequences.

## 5. One-sentence report phrase

A negative LAG sequence error in mlx5e TC cleanup can be used as an index into the peer flow list during eswitch or representor teardown, causing out-of-bounds list access and a kernel crash, with practical triggering usually requiring local device-management privileges.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the proven impact is DoS, but the root cause is an unchecked negative index into a kernel driver array followed by list traversal. This is an OOB access candidate in a privileged networking driver path and should be manually checked before being auto-closed.

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

Patch: net/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable [ Upstream
Commit: 5a95aa0198af75047d98fb72950642c89dab770f
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a95aa0198af75047d98fb72950642c89dab770f

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en_tc.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=5a95aa0198af75047d98fb72950642c89dab770f

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

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

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:H/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: 2
  Paranoid ActionableScore: 3

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 REGULAR

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