{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93159 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93159 is a 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-93159 and fix it if it is affected.\n\nWhat it is: CVE-2026-93159 is a 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-93159 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-93159/ (Markdown: https://insights.sbomify.com/CVE-2026-93159/index.md)","id":"CVE-2026-93159","markdown":"https://insights.sbomify.com/CVE-2026-93159/index.md","name":"CVE-2026-93159","record":{"aliases":["AZL-102479","BELL-CVE-2026-93159","DEBIAN-CVE-2026-93159","GHSA-4wj4-h74m-5rjv","UBUNTU-CVE-2026-93159"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A local attacker can read uninitialized kernel memory via the atmel-sha204a crypto driver when I2C transfers fail, potentially exposing sensitive data.","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: atmel-sha204a - fix heap info leak on I2C transfer failure\n\nThe nonblocking RNG path allocates a work_data structure to track the\nstate of an in-flight asynchronous I2C request. This pointer is stored\nin rng-\u003epriv and later consumed by the read path once the transaction\ncompletes.\n\nIf the underlying I2C transfer fails, the completion callback is invoked\nwith a non-zero status. In this case, the allocated work_data is not\nusable for producing RNG output and must not remain associated with the\nhwrng state.\n\nPreviously, the failure path only logged a warning but left the pointer\nstate uncleared, which can result in subsequent read attempts observing\nstale state and interpreting it as valid completion data.\n\nFix this by freeing the pending work_data. The I2C transaction reports\nan error. This ensures that failed requests do not leave residual state\nbehind that could be interpreted as valid RNG data on later reads.\nClearing rng-\u003epriv is done at the subsequent call to nonblocking read.","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: atmel-sha204a - fix heap info leak on I2C transfer failure","id":"CVE-2026-93159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"crypto: atmel-ecc - reject hardware ECDH without a public key","id":"CVE-2026-93160"},"packages":[],"prev":{"headline":"crypto: sa2ul - stop probe if context pool creation fails","id":"CVE-2026-93158"},"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":"A local attacker can read uninitialized kernel memory via the atmel-sha204a crypto driver when I2C transfers fail, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-93159/"}