[CVE-2026-80657][LOW] accel/amdxdna: Guard management mailbox channel cleanup against NULL pointer [ Upstream

[CVE-2026-80657][LOW] accel/amdxdna: Guard management mailbox channel cleanup against NULL pointer [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80657
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: accel/amdxdna: Guard management mailbox channel cleanup against NULL pointer [ Upstream
Commit: 83d6d375f357ed2702b28d739511aad56d485de7
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=83d6d375f357ed2702b28d739511aad56d485de7
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80657
Analysis date: Fri, 28 Aug 2026 04:21:03 -0400
ActionableScore: 2
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-80657 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80657

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-80657	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	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 'A NULL pointer dereference can occur in the amdxdna mailbox cleanup path because xdna_mailbox_free_channel() and xdna_mailbox_stop_channel() may be called after the management mailbox channel has already been destroyed. This can happen during driver error handling and can crash the kernel when cleanup code dereferences the missing channel. For the CVSS the PR:L is used only for the paranoid score because a reduced privilege local process might indirectly trigger device or runtime error paths in some deployments, while the typical reliable trigger is administrative driver or device management. The issue is not network reachable and requires local interaction with a system that has the affected AMD XDNA accelerator driver and hardware. Impact is denial of service via kernel crash only.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-80657 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	SIMPLEFIX ERRORPATH HARDWARE 	-	-	checked

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

ActionableScore=2
ActionableScoreLower=0

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

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. The patch prevents NULL dereference in cleanup helpers that can be reached from error handling paths.
* Firmware-mediated external influence: +1 for paranoid only. The affected path is tied to an AMD XDNA hardware mailbox and device error handling, but attacker control over firmware or device state is not shown.
* Local unprivileged trigger: +1 for paranoid only. Some accelerator device interfaces may be reachable by local users, but the supplied patch does not show that an unprivileged user can reliably force this cleanup path.
* Requires admin/root/CAP_* in typical deployments: -2 for conservative. Reliable triggering likely involves probe, remove, reset, driver management, or device error handling.
* Rare AND difficult-to-reach subsystem/configuration: -1. Requires affected AMD XDNA accelerator hardware and driver path.
* Hard or unreliable trigger: -1. The crash requires a partially failed cleanup state where mgmt_chann has already been destroyed.

3. Reachability analysis
The bug is local and device dependent. It is not network reachable. Conservative triggering likely requires administrative driver or device management, such as probe failure, reset, remove, or error recovery. A paranoid interpretation allows that a reduced privilege local process with access to the accelerator device might indirectly contribute to runtime error paths, but this is not demonstrated by the patch. Namespaces or containers do not obviously lower the requirement unless the device node is explicitly delegated into the container.

4. Severity interpretation
This behaves like ordinary Moderate or Low-like kernel hardening, not an Important candidate. The primitive is a NULL pointer dereference, not UAF, OOB write, double free, type confusion, or page ownership corruption. The realistic impact is kernel crash or driver level DoS. Theoretical privilege escalation is not supported by the patch context.

5. One-sentence report phrase
A NULL pointer dereference in amdxdna mailbox cleanup can occur when cleanup helpers are called after the management mailbox channel was already destroyed. For the CVSS the PR:L applies only to a paranoid deployment where a reduced privilege local process can indirectly trigger device error paths. The issue is not network reachable and impact is denial of service via kernel crash only.

6. Manual review recommendation
NO MANUAL CHECK NEEDED

Reason: no concrete memory corruption primitive, no network exposure, no demonstrated privilege escalation path, and the affected code is a hardware specific cleanup error path.

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

Patch: accel/amdxdna: Guard management mailbox channel cleanup against NULL pointer [ Upstream
Commit: 83d6d375f357ed2702b28d739511aad56d485de7
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=83d6d375f357ed2702b28d739511aad56d485de7

Changed files:
  drivers/accel/amdxdna/amdxdna_mailbox.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=83d6d375f357ed2702b28d739511aad56d485de7

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

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

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

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