{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80522 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-80522 is a high-severity vulnerability in Linux, published on 26 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-80522 and fix it if it is affected.\n\nWhat it is: CVE-2026-80522 is a high-severity vulnerability in Linux, published on 26 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-80522 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80522/ (Markdown: https://insights.sbomify.com/CVE-2026-80522/index.md)","id":"CVE-2026-80522","markdown":"https://insights.sbomify.com/CVE-2026-80522/index.md","name":"CVE-2026-80522","record":{"aliases":["BELL-CVE-2026-80522","DEBIAN-CVE-2026-80522","GHSA-fhv2-cf5f-4mpm","UBUNTU-CVE-2026-80522"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req()\n\nPerform rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req() the same way\nit is done in tegra_ccm_crypt_init(). The current formulae may lead to a\ncrash if a caller does not call tegra_gcm_setauthsize() and so ctx-\u003eauthsize\nremains zero. Then a decrypt operation with incorrect rctx-\u003ecryptlen will\nlead to a write beyound rctx-\u003edst_sg buffer.\n\nAs a follow-up cleanup delete struct tegra_aead_ctx-\u003eauthsize field since\nit appears to be completely unused. Also simplify tegra_ccm_setauthsize()\nand tegra_gcm_setauthsize() functions respectively.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"crypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req()","id":"CVE-2026-80522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"clk: spacemit: k3: set hdma clock as critical","id":"CVE-2026-80523"},"packages":[],"prev":{"headline":"af_unix: Unlink scc_entry in unix_del_edge().","id":"CVE-2026-80521"},"products":["Linux"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-80522/"}