← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-90069

Last refreshed2026-10-19

Status: UPDATED  |  Advisory ID: CVE-2026-90069

Key Details

CVECVE-2026-90069
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-19
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In 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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-90069
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-90069
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.