GHSA-83J8-G3F3-XGRF
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-18 18:31In the Linux kernel, the following vulnerability has been resolved:
crypto: acomp - allocate async request context when cloning
ACOMP_REQUEST_ON_STACK() reserves only enough storage for the synchronous fallback. When an async implementation is selected, callers clone that stack request before retrying, but acomp_request_clone() currently copies only the stack-sized object. The clone therefore has no storage for the async provider request context, and providers such as QAT write past the allocation through acomp_request_ctx(). KASAN does report a slab OOB write.
Allocate a zeroed clone large enough for the runtime acomp request size, copy only the bytes present in the source object, and preserve the existing fallback-on-allocation-failure behavior. Use the runtime reqsize because an implementation may adjust it during tfm initialization.
{
"affected": [],
"aliases": [
"CVE-2026-90069"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:16:55Z",
"severity": "HIGH"
},
"details": "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.",
"id": "GHSA-83j8-g3f3-xgrf",
"modified": "2026-09-18T18:31:26Z",
"published": "2026-09-17T18:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90069"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/889fa17a0af09ff93a9166abc82ee7a654faa49b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d48197cbd5d3476c7deea644972e9ec510865ec2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee440d4fc0d2f15894ab1f64c474a3adbc858880"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.