[CVE-2026-80882][MODERATE REGULAR] crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm [ Upstream

[CVE-2026-80882][MODERATE REGULAR] crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80882
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm [ Upstream
Commit: 5cf0f624191cd12bd0a376bd7850d63b2b2236d4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5cf0f624191cd12bd0a376bd7850d63b2b2236d4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80882
Analysis date: Fri, 04 Sep 2026 16:51:02 -0400
ActionableScore: 3
ActionableScore lower bound: 1
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
A Tegra CCM crypto request could be finalized with an incorrect status when input DMA buffer allocation fails, potentially causing callers to trust a failed crypto operation, with local reachability through Crypto API consumers and no evidence of memory corruption or direct privilege escalation.

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

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

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-80882	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-80882 CHECK WITH IMPACT FROM ORIG NN NONE	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:L';CWE-703;CWE-755;*CWE-457;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N';BEST CVSS score: '4.5';DESCR 'The Tegra CCM crypto path can finalize a request with an incorrect status when dma_alloc_coherent fails for the input buffer because ret is not set to ENOMEM before the error path. This is an error handling bug in the crypto request flow rather than a memory corruption primitive. For the CVSS the PR:L is used because a local user or local process would normally need access to a Crypto API consumer such as AF_ALG or another kernel path using this driver. AC:H is used because reliable triggering depends on allocation failure or memory pressure on a system with the Tegra crypto engine and CCM enabled. The issue is not directly network reachable. Impact is mainly incorrect crypto operation status and possible integrity impact if a caller trusts a request that should have failed. A limited confidentiality or availability impact is only a conservative worst case and is not supported by a concrete memory corruption primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 2)	YES	NOMEMCHK SIMPLEFIX LINUS MEMORY  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	YES	NO	checked

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

ActionableScore=3
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 3
* Final recommended bucket: **Borderline, manual review recommended**::

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1. A local process may reach the crypto operation through AF_ALG or another local Crypto API consumer if the Tegra CCM implementation is exposed.
* Integrity impact plausible: +1. The request may be finalized with an incorrect status after input buffer allocation failure, so a caller could treat a failed crypto operation as successful.
* Rare hardware or configuration dependency: -1. The affected path requires Tegra crypto hardware and the specific CCM driver path.
* Hard or unreliable condition: -1. Reliable triggering depends on dma_alloc_coherent failure or memory pressure, not only on normal request submission.

Paranoid additional signals:

* Local unprivileged high-control kernel data-plane API refinement: +1. If AF_ALG exposes this algorithm to local users, request sizes and crypto operations are user-influenced.
* Confidentiality impact plausible: +1. In a conservative worst case, incorrect crypto completion status could affect consumers that rely on CCM authentication or encryption results.
* Availability impact realistic: +1. In a worst case, repeated failed crypto operations or confused callers could cause service-level disruption, but no kernel crash is shown.

Not awarded:

* No generic memory corruption. The patch does not show UAF, OOB write, double free, type confusion, refcount misuse, or arbitrary write.
* No strong DoS. The patch does not show panic, oops, deadlock, or persistent system-wide failure.
* No privilege escalation signal. There is no demonstrated reclaim, overwrite, callback control, or security-boundary bypass.

## 3. Reachability analysis

The likely trigger is local, through a Crypto API consumer such as AF_ALG or an in-kernel user of the Tegra CCM implementation. The issue is not network reachable by itself. Namespaces do not materially improve reachability unless the affected crypto interface is exposed inside the container and backed by the host Tegra driver. The path is hardware and driver specific, so exposure is limited to systems using Tegra SE AES with CCM enabled. Practical triggering also requires an allocation failure, making exploitation less reliable than ordinary local API misuse.

Call-site confidence: medium. The changed function and error path are visible, but not all external Crypto API consumers are shown in the supplied patch.

## 4. Severity interpretation

This behaves more like a low-end Moderate or borderline issue than an Important vulnerability. The realistic impact is incorrect crypto request completion status after allocation failure, with possible integrity impact for callers that trust the result. Theoretical confidentiality or availability impact is possible in a paranoid interpretation, but the patch does not support memory corruption, LPE, or a reliable kernel crash primitive.

## 5. One-sentence report phrase

A Tegra CCM crypto request could be finalized with an incorrect status when input DMA buffer allocation fails, potentially causing callers to trust a failed crypto operation, with local reachability through Crypto API consumers and no evidence of memory corruption or direct privilege escalation.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the score is low, but crypto error handling with a possible silent success path is security-sensitive enough to review manually, especially if AF_ALG exposes the affected algorithm to unprivileged local users on the evaluated product.

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

Patch: crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm [ Upstream
Commit: 5cf0f624191cd12bd0a376bd7850d63b2b2236d4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5cf0f624191cd12bd0a376bd7850d63b2b2236d4

Changed files:
  drivers/crypto/tegra/tegra-se-aes.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=5cf0f624191cd12bd0a376bd7850d63b2b2236d4

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

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

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:L/UI:N/S:U/C:N/I:L/A:N
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
  The Best / paranoid CVSS score: 4.5

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