{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80832 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80832 is a memory corruption vulnerability in Linux, published on 4 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-80832 and fix it if it is affected.\n\nWhat it is: CVE-2026-80832 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-80832 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-80832/ (Markdown: https://insights.sbomify.com/CVE-2026-80832/index.md)","id":"CVE-2026-80832","markdown":"https://insights.sbomify.com/CVE-2026-80832/index.md","name":"CVE-2026-80832","record":{"aliases":["AZL-99567","BELL-CVE-2026-80832","DEBIAN-CVE-2026-80832","GHSA-5ch2-359f-fp8j","UBUNTU-CVE-2026-80832"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel crypto","requires_auth":"none","summary":"A buffer underallocation in the Linux kernel QCE crypto driver allows out-of-bounds reads, potentially causing denial of service or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qce - fix CCM AAD buffer underallocation\n\nThe AAD buffer allocated in qce_aead_ccm_prepare_buf_assoclen()\ncan be smaller than the length later programmed into the DMA\nscatterlist.\n\nThe allocation size is currently calculated as:\n\n  ALIGN(assoclen, 16) + MAX_CCM_ADATA_HEADER_LEN\n\nwhile the DMA length is set to:\n\n  ALIGN(assoclen + adata_header_len, 16)\n\nSince ALIGN() does not distribute over addition, the allocation\ncan be smaller than the DMA length. For example, when\nassoclen = 32 and adata_header_len = 2:\n\n  allocation = ALIGN(32, 16) + 6 = 38\n  DMA length = ALIGN(32 + 2, 16) = 48\n\nAs a result, the QCE hardware can read beyond the allocated\nbuffer while computing the CBC-MAC over the associated data.\nThe extra bytes are folded into the authentication tag,\nresulting in an incorrect tag and causing CCM self-test\nfailures such as:\n\n  alg: aead: ccm-aes-qce encryption test failed (wrong result)\n  on test vector 8\n\nFix the allocation by adding the maximum possible AAD header\nlength before alignment:\n\n  ALIGN(assoclen + MAX_CCM_ADATA_HEADER_LEN, 16)\n\nThis guarantees that the allocated buffer is large enough\nfor the fully padded AAD data for all supported header sizes.","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: qce - fix CCM AAD buffer underallocation","id":"CVE-2026-80832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"crypto: sun8i-ss - Remove crypto_rng interface","id":"CVE-2026-80833"},"packages":[],"prev":{"headline":"crypto: mxs-dcp - fix source scatterlist length access","id":"CVE-2026-80831"},"products":["Linux"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A buffer underallocation in the Linux kernel QCE crypto driver allows out-of-bounds reads, potentially causing denial of service or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-80832/"}