{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93161 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93161 is a vulnerability in Linux, published on 17 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-93161 and fix it if it is affected.\n\nWhat it is: CVE-2026-93161 is a vulnerability in Linux, published on 17 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-93161 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-93161/ (Markdown: https://insights.sbomify.com/CVE-2026-93161/index.md)","id":"CVE-2026-93161","markdown":"https://insights.sbomify.com/CVE-2026-93161/index.md","name":"CVE-2026-93161","record":{"aliases":["AZL-102084","BELL-CVE-2026-93161","DEBIAN-CVE-2026-93161","GHSA-jc96-xj7h-vxxp","UBUNTU-CVE-2026-93161"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker with local access could potentially read sensitive AES key material from the kernel stack due to insufficient memory clearing.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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: qat - clear AES key schedule from stack\n\nqat_alg_xts_reverse_key() expands the forward XTS AES key on the stack.\nThat schedule contains key material and can remain in the stack frame.\n\nClear the temporary crypto_aes_ctx with memzero_explicit() after the copy.","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: qat - clear AES key schedule from stack","id":"CVE-2026-93161","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"crypto: qat - cancel work on re-enable SR-IOV timeout","id":"CVE-2026-93162"},"packages":[],"prev":{"headline":"crypto: atmel-ecc - reject hardware ECDH without a public key","id":"CVE-2026-93160"},"products":["Linux"],"published":"2026-09-17","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":"An attacker with local access could potentially read sensitive AES key material from the kernel stack due to insufficient memory clearing.","url":"https://insights.sbomify.com/CVE-2026-93161/"}