{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90069 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90069 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90069 and fix it if it is affected.\n\nWhat it is: CVE-2026-90069 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90069 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-90069/ (Markdown: https://insights.sbomify.com/CVE-2026-90069/index.md)","id":"CVE-2026-90069","markdown":"https://insights.sbomify.com/CVE-2026-90069/index.md","name":"CVE-2026-90069","record":{"aliases":["BELL-CVE-2026-90069","DEBIAN-CVE-2026-90069","GHSA-83j8-g3f3-xgrf","UBUNTU-CVE-2026-90069"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel crypto","requires_auth":"low_privilege","summary":"A memory corruption vulnerability in the Linux kernel crypto subsystem allows out-of-bounds writes, potentially leading to code execution or system crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","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: acomp - allocate async request context when cloning\n\nACOMP_REQUEST_ON_STACK() reserves only enough storage for the\nsynchronous fallback. When an async implementation is selected, callers\nclone that stack request before retrying, but acomp_request_clone()\ncurrently copies only the stack-sized object. The clone therefore has no\nstorage for the async provider request context, and providers such as QAT\nwrite past the allocation through acomp_request_ctx(). KASAN does report\na slab OOB write.\n\nAllocate a zeroed clone large enough for the runtime acomp request size,\ncopy only the bytes present in the source object, and preserve the\nexisting fallback-on-allocation-failure behavior. Use the runtime reqsize\nbecause an implementation may adjust it during tfm initialization.","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: acomp - allocate async request context when cloning","id":"CVE-2026-90069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"tpm: st33zp24: Return zero on status read failure","id":"CVE-2026-90070"},"packages":[],"prev":{"headline":"ASoC: dapm: Fix off-by-one check on the second enum channel","id":"CVE-2026-90068"},"products":["Linux"],"published":"2026-09-17","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A memory corruption vulnerability in the Linux kernel crypto subsystem allows out-of-bounds writes, potentially leading to code execution or system crashes.","url":"https://insights.sbomify.com/CVE-2026-90069/"}