GHSA-4WJ4-H74M-5RJV
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
crypto: atmel-sha204a - fix heap info leak on I2C transfer failure
The nonblocking RNG path allocates a work_data structure to track the state of an in-flight asynchronous I2C request. This pointer is stored in rng->priv and later consumed by the read path once the transaction completes.
If the underlying I2C transfer fails, the completion callback is invoked with a non-zero status. In this case, the allocated work_data is not usable for producing RNG output and must not remain associated with the hwrng state.
Previously, the failure path only logged a warning but left the pointer state uncleared, which can result in subsequent read attempts observing stale state and interpreting it as valid completion data.
Fix this by freeing the pending work_data. The I2C transaction reports an error. This ensures that failed requests do not leave residual state behind that could be interpreted as valid RNG data on later reads. Clearing rng->priv is done at the subsequent call to nonblocking read.
{
"affected": [],
"aliases": [
"CVE-2026-93159"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:11Z",
"severity": null
},
"details": "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.",
"id": "GHSA-4wj4-h74m-5rjv",
"modified": "2026-09-17T18:32:12Z",
"published": "2026-09-17T18:32:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93159"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0d6db386133d9230befb77967bbf130443964860"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/28cc179252347718f97045dd5ea74165609dbd7d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4e76d85e505b7451925efbcd67c015e8c2440c68"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/72bbf11ba14bd7d5fbf31a1ec42fff608b657f74"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/94abda77b57a35b82bba0365bad072d94d67ffe9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a430b5b6d2ddd2b266330f8507a655be1148347d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bcac9052e19490231ff6e0678a06bd2fcf8db3af"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f4d347fb1309b69ea6f817a17e6b2893c8d754b7"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.