CVE-2026-93161: Linux kernel · crypto: qat – clear AES key schedule from stack
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fb1194b78a163cc56bb9480c707fc34b53522359 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fb1194b78a163cc56bb9480c707fc34b53522359, dcaa0f1e86cbcb01f68131ae907b54cf299a3592, d41a9fcfb7f9ee36e4a4aaf5e7996bca6be1e7a9 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. The patch explicitly clears the AES key schedule from the stack using memzero_explicit() after use. Users and administrators should update to a fixed Linux kernel version containing the patch identified by the commits listed in establishedFacts.fixedVersions.
Description
A vulnerability in the Linux kernel's crypto qat module was addressed by clearing the AES key schedule from the stack after use. The function qat_alg_xts_reverse_key() expanded the forward XTS AES key on the stack, leaving sensitive key material in memory. The fix involves explicitly zeroing out the temporary AES context to prevent key material from lingering in stack memory.
References
- git.kernel.org/stable/c/b9cf42622b30178f554fa74411eec67e02d70411 (opens in a new tab)
- git.kernel.org/stable/c/fb1194b78a163cc56bb9480c707fc34b53522359 (opens in a new tab)
- git.kernel.org/stable/c/892f34dc1819cceb8841005a68086710ce3763b6 (opens in a new tab)
- git.kernel.org/stable/c/dcaa0f1e86cbcb01f68131ae907b54cf299a3592 (opens in a new tab)
- git.kernel.org/stable/c/9af019e213ada5c3d0d33c515071a1414b6899f3 (opens in a new tab)
- git.kernel.org/stable/c/92e4979e1a770860b26aa3d90cce0c4c6a53833c (opens in a new tab)
- git.kernel.org/stable/c/d41a9fcfb7f9ee36e4a4aaf5e7996bca6be1e7a9 (opens in a new tab)