Look up another CVE · open CVE-2026-80522 in the interactive tracker
CVE-2026-80522
crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req()
Published 2026-08-26 (2 months ago) by the Linux kernel CNA. Subsystem drivers/crypto. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80522 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.105-1 | Update the kernel and reboot. Fixed in 6.12.105-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4788-1 · 2026-09-19 · text | 6.12.107-1~deb12u1 | Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Perform rctx->cryptlen calculation in tegra_gcm_do_one_req() the same way it is done in tegra_ccm_crypt_init(). The current formulae may lead to a crash if a caller does not call tegra_gcm_setauthsize() and so ctx->authsize remains zero. Then a decrypt operation with incorrect rctx->cryptlen will lead to a write beyound rctx->dst_sg buffer. As a follow-up cleanup delete struct tegra_aead_ctx->authsize field since it appears to be completely unused. Also simplify tegra_ccm_setauthsize() and tegra_gcm_setauthsize() functions respectively.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/crypto/tegra/tegra-se-aes.c
- What this is
- TEGRA CRYPTO DRIVERSMAINTAINERS section matched on drivers/crypto/tegra/* · Supported
Check it on the machine
grep -wE 'CONFIG_CRYPTO|CONFIG_CRYPTO_DEV_TEGRA' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code in 4 releases. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sid, bookworm · linux-6.12n
- ?
- not established - no Makefile entry for the affected file
- n
- not enabled on any flavour - this release does not build the code
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_CRYPTO, CONFIG_CRYPTO_DEV_TEGRA
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-26 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/crypto
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.10 | 6.12.105 | cd6991001bf0 |
| 6.10 | 6.18.46 | 99a18e1d979e |
| 6.10 | 7.1.10 | c6237834d999 |
| 6.10 | 7.2 | 360f2974fcea |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4788-1 | 2026-09-19 | bookworm 6.12.107-1~deb12u1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The flaw is in the Tegra Security Engine gcm(aes) driver reached via the kernel crypto API (AF_ALG socket syscalls); major network consumers call setauthsize and are not affected, and the driver only exists on Tegra234 platforms with TEGRA_HOST1X.
- AC:LAttack complexity, low
- On affected Tegra systems with tegra-se loaded, an attacker reliably triggers the bug by issuing a GCM decrypt through AF_ALG without calling ALG_SET_AEAD_AUTHSIZE, relying on the default 16-byte tag while ctx->authsize remains zero.
- PR:LPrivileges required, low
- Triggering tegra GCM decrypt via AF_ALG requires only an unprivileged local user able to open AF_ALG sockets and bind to gcm(aes); no CAP_SYS_ADMIN, real root, or container-escaping capabilities are needed on standard configurations.
- UI:NUser interaction, none
- Exploitation requires no victim interaction such as mounting filesystems or opening files; the attacker directly submits crafted decrypt requests through the local crypto interface.
- S:UScope, unchanged
- Impact is kernel heap/memory corruption and potential privilege escalation within the same kernel security domain; it does not cross VM, container, or IOMMU boundaries.
- C:HConfidentiality impact, high
- The out-of-bounds write corrupts memory adjacent to the destination scatterlist buffer; such heap corruption can expose kernel pointers or other sensitive data and is rated High per memory-corruption guidance.
- I:HIntegrity impact, high
- Decrypt uses an inflated cryptlen so scatterwalk_map_and_copy writes up to 16 bytes beyond the caller-allocated dst_sg buffer with no bounds checking, constituting an exploitable out-of-bounds write primitive.
- A:HAvailability impact, high
- Writing past the destination scatterlist can corrupt adjacent kernel structures and cause kernel oops or panic; the fix commit explicitly describes this as a crash-causing out-of-bounds write condition.