[CVE-2026-45907][MODERATE REGULAR] net/mlx5e: Fix deadlocks between devlink and netdev instance locks [ Upstream

[CVE-2026-45907][MODERATE REGULAR] net/mlx5e: Fix deadlocks between devlink and netdev instance locks [ Upstream

[AL-KERNEL]

CVE: CVE-2026-45907
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: Fix deadlocks between devlink and netdev instance locks [ Upstream
Commit: 4329514c61abefe4961541b128c549b017bab5ad
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4329514c61abefe4961541b128c549b017bab5ad
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45907
Analysis date: Wed, 27 May 2026 22:01:15 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
An mlx5e health recovery lock-ordering bug can deadlock devlink and netdev instance locks during recovery or teardown, causing local or operator-triggered network interface DoS.

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

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

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-45907	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-667;*CWE-833;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'mlx5e health recovery could acquire the netdev instance lock before reporting through devlink, reversing the expected devlink to rtnl to netdev lock order and allowing recovery or teardown paths to deadlock. The affected paths include TX error CQE recovery, RX timeout recovery, PTP SQ unhealthy recovery, and TX timeout recovery. For the CVSS the PR:L is used in the paranoid score because reduced privilege service accounts or delegated operators may control mlx5e recovery or netdev management in some deployments, although reliable triggering usually requires administrative device management or fault injection. The issue is not directly network reachable. Impact is denial of service through stuck driver recovery, blocked teardown, or loss of network interface availability. No supported evidence indicates information disclosure, integrity impact, kernel memory corruption, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3) 	MAYBE	REMOTE LOCK DEADLOCK DANGER NETWORK  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 4
* Final recommended bucket: **Borderline, manual review recommended**::

## 2. Signal breakdown

* Availability impact realistic: +1
  Incorrect lock ordering can deadlock mlx5e health recovery or teardown paths, potentially leaving the network interface unavailable.

* Reliable kernel crash / strong DoS: +1
  Not a crash, but a driver deadlock in recovery/teardown is a strong availability failure for affected systems.

* Broad or high-value deployment exposure: +1 in paranoid scoring
  mlx5e is widely used in datacenter and cloud networking environments, though the affected path is not generic packet receive.

* Privileged device-management or recovery path: +1 in paranoid scoring
  The issue occurs in trusted driver health recovery and device-management contexts.

* Requires admin or delegated device management in typical deployments: -2 conservative
  Reliable triggering usually requires devlink/netdev operations, teardown, fault injection, or hardware error conditions.

* Hard or special triggering conditions: -1
  The deadlock needs overlap between health reporter recovery and netdev/devlink locking paths.

* No memory corruption: +0
  The patch fixes lock ordering, not UAF, OOB write, arbitrary write, or lifetime corruption.

* No direct remote reachability: +0
  Network traffic or device errors can contribute to recovery events, but the patch does not show a packet-triggerable vulnerability.

## 3. Reachability analysis

The issue is reachable when mlx5e health reporter recovery runs concurrently with teardown or management paths that involve devlink and netdev instance locks. In normal deployments, reliable triggering is usually limited to administrators, operators, or fault conditions. In cloud or containerized environments, delegated operators or service accounts with netdev or devlink access may lower practical privilege.

The path is not directly network reachable. Remote traffic may contribute to device stress or error conditions, but there is no evidence that packets alone can reliably trigger the deadlock.

## 4. Severity interpretation

This is a borderline Moderate availability issue. It is operationally important for mlx5e deployments because a deadlocked recovery path can affect network availability, but it is not memory corruption, not an LPE primitive, and not a demonstrated remote packet-processing bug. Manual review is useful mainly for products where mlx5e devices are critical or where devlink/netdev operations are delegated.

## 5. One-sentence report phrase

An mlx5e health recovery lock-ordering bug can deadlock devlink and netdev instance locks during recovery or teardown, causing local or operator-triggered network interface DoS.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Manual review is recommended for systems using mlx5e in critical networking roles or exposing devlink/netdev management to delegated operators. Otherwise this is a privileged, availability-only driver deadlock.

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

Patch: net/mlx5e: Fix deadlocks between devlink and netdev instance locks [ Upstream
Commit: 4329514c61abefe4961541b128c549b017bab5ad
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4329514c61abefe4961541b128c549b017bab5ad

Changed files:
  drivers/net/ethernet/mellanox/mlx5/core/en/ptp.c
  drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c
  net/netdev_lock.h
  drivers/net/ethernet/mellanox/mlx5/core/en/reporter_tx.c
  drivers/net/ethernet/mellanox/mlx5/core/en_main.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=4329514c61abefe4961541b128c549b017bab5ad

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

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

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:H/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:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

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: 4

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