From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80882: crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm
Date: Fri, 4 Sep 2026 18:46:49 +0200 [thread overview]
Message-ID: <2026090437-CVE-2026-80882-2aeb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm
Ensure the ENOMEM error value is set when the input buffer allocation
fails in tegra_ccm_do_one_req.
The Linux kernel CVE team has assigned CVE-2026-80882 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12.91 with commit 23f03ebd52f07418a8e3143d944b4a40552645d4 and fixed in 6.12.97 with commit 5cf0f624191cd12bd0a376bd7850d63b2b2236d4
Issue introduced in 6.15 with commit 1e245948ca0c252f561792fabb45de5518301d97 and fixed in 6.18.40 with commit 4f3c17f14cf9085a9c9ae2145f748ea55cf6d4e9
Issue introduced in 6.15 with commit 1e245948ca0c252f561792fabb45de5518301d97 and fixed in 7.1.5 with commit 20360e125a8dd411b0cc2660cb70f58590740818
Issue introduced in 6.15 with commit 1e245948ca0c252f561792fabb45de5518301d97 and fixed in 7.2 with commit 690a5f9e5c972a580565ce544ed1627ccf1e84de
Issue introduced in 6.13.11 with commit bd12207bd1fc95009029d7943cb973c787c874a4
Issue introduced in 6.14.2 with commit 3ba914ad4991be67a4ff88ecaa388bafb55de298
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80882
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/crypto/tegra/tegra-se-aes.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/5cf0f624191cd12bd0a376bd7850d63b2b2236d4
https://git.kernel.org/stable/c/4f3c17f14cf9085a9c9ae2145f748ea55cf6d4e9
https://git.kernel.org/stable/c/20360e125a8dd411b0cc2660cb70f58590740818
https://git.kernel.org/stable/c/690a5f9e5c972a580565ce544ed1627ccf1e84de
reply other threads:[~2026-09-04 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026090437-CVE-2026-80882-2aeb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.