[CVE-2026-97962][MODERATE REGULAR] net/mlx5e: Move representor vnic reporter to eswitch devlink port [ Upstream

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

CVE: CVE-2026-97962
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net/mlx5e: Move representor vnic reporter to eswitch devlink port [ Upstream
Commit: dcaba72c85c14fe7393a59d61695941e6ccbd7d7
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dcaba72c85c14fe7393a59d61695941e6ccbd7d7
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97962
Analysis date: Fri, 25 Sep 2026 13:25:04 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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

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

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

CVE-2026-97962	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-97962 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-667;CWE-362;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'The mlx5e representor vnic health reporter can be destroyed from the representor netdev unload path without holding the devlink instance lock. A concurrent devlink health operation may overlap reporter destruction and create a reporter lifetime race, while the directly demonstrated result is a devl_assert_locked warning during driver unbind. For the CVSS the PR:L value is used for the paranoid score because devlink or device management may be delegated to a reduced capability root, container service, or network management account. Reliable triggering on ordinary hosts usually requires stronger administrative control over driver unbind. AC:H reflects the need to hit a concurrent lifecycle window. The issue is not directly reachable through ordinary network packets. Impact is at least local denial of service or management path disruption, with limited confidentiality or integrity impact considered only as a conservative possibility if concurrent reporter access exposes a stale object.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)  SKIP CVE-2026-97962 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE NETWORK HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	-	-	checked

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

ActionableScore=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=YES
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate**::

No floor or cap was applied.

2. Signal breakdown

* +1 Weak indirect lifetime or synchronization concern. The reporter is destroyed outside the devlink instance lock required to serialize its lifecycle.
* -2 Proven host-admin-equivalent trigger. The demonstrated path is PCI driver unbind through `unbind_store`, executed by UID 0 against a host-owned mlx5 device.
* +1 was not awarded for kernel crash or strong DoS. The demonstrated consequence is a `devl_assert_locked()` WARN splat, and WARN alone scores zero.
* Real UAF was not awarded. The evidence does not show that a reporter or its private object is freed and subsequently accessed.
* Structured stale-object leverage was not awarded. No stale callback invocation, reclaimed object, post-free field consumption, or lifetime mutation is established.
* Controlled reclaim, arbitrary write, disclosure, privilege escalation, and remote packet reachability are not demonstrated.
* Confidentiality and integrity points were not awarded. The previous proposed `C:L/I:L` interpretation requires a stale-object operation that is not established by the supplied code.
* No additional availability point was awarded because no crash, persistent device failure, or independently distinct availability consequence is shown.

3. Reachability analysis

The demonstrated trigger is mlx5 driver unbind on a host-owned PCI device. That operation requires host administrative control and is not an attacker-created namespace operation. Devlink commands may sometimes be delegated, but a delegated devlink user is not shown to control the required driver-unbind stage, so separate actors cannot be combined into a single PR:L attacker.

The complete trigger is therefore not namespace-scoped. It requires an mlx5 eswitch with representor support and an existing vnic health reporter, but no rare-hardware penalty is applied merely because this is driver-specific. No direct network-packet trigger exists. A concurrent devlink operation could theoretically expose a deeper race, but the supplied context neither demonstrates such an interleaving nor establishes that it produces post-lifetime access.

4. Primitive and severity interpretation

The exact established defect is violation of the devlink locking contract during reporter destruction. The observable result is a lock assertion warning during representor teardown. This is CLASS_C invalid-state or synchronization behavior, not a proven CLASS_B lifetime violation.

The reporter is an active structured object, but object complexity alone does not establish UAF leverage. There is no visible first operation ending the reporter or private-object lifetime followed by a stale dereference, repeated release, callback, or refcount mutation. No concrete repeated release operation exists.

A concurrent reporter-lifetime bug remains a theoretical issue requiring limited source review, but it is not evidence-supported enough to score as UAF or memory corruption. ImportantCandidate is therefore NO. AutoDowngradeAllowed is YES because the established behavior is a host-admin-triggered warning without an unresolved concrete corruption primitive.

5. One-sentence report phrase

The mlx5e representor teardown destroys a vnic health reporter without the required devlink instance lock, producing a host-admin-triggered lock assertion warning but no demonstrated use-after-free, kernel crash, or remotely reachable security primitive.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Review concurrent devlink health-report operations around reporter destruction to confirm that the missing lock cannot permit callback execution or private-object access after teardown. The supplied patch alone does not establish that outcome.

7. Call-site confidence

Call-site confidence: medium

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

Patch: net/mlx5e: Move representor vnic reporter to eswitch devlink port [ Upstream
Commit: dcaba72c85c14fe7393a59d61695941e6ccbd7d7
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dcaba72c85c14fe7393a59d61695941e6ccbd7d7

Changed files:
  net/devlink/core.c
  drivers/net/ethernet/mellanox/mlx5/core/en_rep.c
  lib/vxlan.h
  drivers/net/ethernet/mellanox/mlx5/core/en_rep.h
  drivers/net/ethernet/mellanox/mlx5/core/esw/devlink_port.c
  drivers/net/ethernet/mellanox/mlx5/core/eswitch.h

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=dcaba72c85c14fe7393a59d61695941e6ccbd7d7

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

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

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: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: unknown
  Paranoid ActionableScore: 0

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