[CVE-2026-53297][LOW] net: mana: Guard mana_remove against double invocation [ Upstream

[CVE-2026-53297][LOW] net: mana: Guard mana_remove against double invocation [ Upstream

[AL-KERNEL]

CVE: CVE-2026-53297
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net: mana: Guard mana_remove against double invocation [ Upstream
Commit: a1ddfd2c0b7a48e5239fadd2a24cc4bc2cda90e6
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a1ddfd2c0b7a48e5239fadd2a24cc4bc2cda90e6
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53297
Analysis date: Fri, 26 Jun 2026 16:33:07 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
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-53297	LOW	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-476;CWE-703;CWE-754;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'mana_remove can be invoked twice after a failed PM resume path in the Microsoft MANA network driver. The first invocation tears down the device and clears gdma_context and driver_data, but the failed resume callback does not automatically unbind the driver. A later driver unbind can call mana_remove again and the old code dereferences gc dev while gc is NULL, causing a kernel panic. For the CVSS the PR:L is used for the paranoid view because some environments may delegate device power management or driver unbind control to a reduced capability administrator or service account. The issue is not directly network reachable and requires local control over device lifecycle or a faulted resume path. Impact is denial of service only via kernel crash.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	REMOTE DANGER SIMPLEFIX NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

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

ActionableScore=1
ActionableScoreLower=0

1. ActionableScore
* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. The second mana_remove() invocation can dereference gc->dev when gc is NULL, causing a kernel panic.
* Firmware-mediated external influence: +1 in paranoid view only. The initial failed resume may depend on device or firmware behavior, but this is not a direct remote or network trigger.
* Requires admin/root/device-management privileges in typical deployments: -2 conservative. Reliable triggering normally requires control over PM resume, driver unbind, or device lifecycle.
* Rare AND difficult-to-reach subsystem/configuration: -1 conservative. This requires Microsoft MANA hardware or environment plus a failed resume followed by unbind.
* No generic memory corruption score. This is a NULL pointer dereference, not UAF, double free, OOB write, stale callback, or attacker-controlled object reuse.
* No LPE, confidentiality, or integrity signals. The patch supports DoS only.

3. Reachability analysis
A typical attacker would need local administrative or delegated device-management control to influence resume failure and later driver unbind. Ordinary unprivileged local users cannot normally invoke this path. Containers or namespaces do not meaningfully lower the requirement unless device power management or driver lifecycle controls are explicitly delegated. The affected driver is relevant mainly on systems using Microsoft MANA devices, commonly cloud or Hyper-V related environments. The path is not packet-triggered and is not realistically network reachable.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like kernel DoS issue. The theoretical impact is a host kernel crash from a NULL pointer dereference. There is no evidence of exploitable memory lifetime corruption, attacker-controlled reclaim, object confusion, write primitive, or privilege escalation. The realistic exploitation condition is narrow and device-lifecycle dependent.

5. One-sentence report phrase
A double invocation of mana_remove() after a failed PM resume can dereference a NULL gdma_context during later driver unbind, causing a local privileged kernel crash DoS on affected Microsoft MANA devices.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The patch shows a straightforward NULL pointer dereference in a privileged device lifecycle path, with no supported LPE or memory corruption primitive beyond crash.

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

Patch: net: mana: Guard mana_remove against double invocation [ Upstream
Commit: a1ddfd2c0b7a48e5239fadd2a24cc4bc2cda90e6
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a1ddfd2c0b7a48e5239fadd2a24cc4bc2cda90e6

Changed files:
  drivers/net/ethernet/microsoft/mana/mana_en.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=a1ddfd2c0b7a48e5239fadd2a24cc4bc2cda90e6

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

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

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

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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