Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80522: crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 360f2974fcea49c61f6d6f81554741a9eeee7168, 99a18e1d979e0fad3aaf9c65ae6696897c1d9869, c6237834d9994de209cb90c7a2c461247bce8e90.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 360f2974fcea49c61f6d6f81554741a9eeee7168, 99a18e1d979e0fad3aaf9c65ae6696897c1d9869, c6237834d9994de209cb90c7a2c461247bce8e90 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req() 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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 26, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80522

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.10affected
    • 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before cd6991001bf0681ed0bcf21f9cc3d261d749b2bbaffected · git
    • 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before 99a18e1d979e0fad3aaf9c65ae6696897c1d9869affected · git
    • 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before c6237834d9994de209cb90c7a2c461247bce8e90affected · git
    • 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0 and later · before 360f2974fcea49c61f6d6f81554741a9eeee7168affected · git
    • before 6.10not affected · semver
    • 6.12.105 and later · up to and including 6.12.*not affected · semver
    • 6.18.46 and later · up to and including 6.18.*not affected · semver
    • 7.1.10 and later · up to and including 7.1.*not affected · semver
    • 7.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74754Aug 26, 2026 · scsi: core: pair EH runtime PM get and put
    0Monitor
  • ← EarlierCVE-2026-80521Aug 26, 2026 · af_unix: Unlink scc_entry in unix_del_edge().
    31Monitor
  • Later →CVE-2026-80524Aug 26, 2026 · optee: ffa: Add NULL check in optee_ffa_lend_protmem
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux360f2974fcea49c61f6d6f81554741a9eeee7168Vendor (CNA)
Linux Linux99a18e1d979e0fad3aaf9c65ae6696897c1d9869Vendor (CNA)
Linux Linuxc6237834d9994de209cb90c7a2c461247bce8e90Vendor (CNA)
Linux Linuxcd6991001bf0681ed0bcf21f9cc3d261d749b2bbVendor (CNA)
almalinux:kernel5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.53.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.105-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-687.53.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records