CVE-2026-93161: crypto: qat - clear AES key schedule from stack
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 892f34dc1819cceb8841005a68086710ce3763b6, 92e4979e1a770860b26aa3d90cce0c4c6a53833c, 9af019e213ada5c3d0d33c515071a1414b6899f3.
Low priority for now. Upgrade to Linux Linux 892f34dc1819cceb8841005a68086710ce3763b6, 92e4979e1a770860b26aa3d90cce0c4c6a53833c, 9af019e213ada5c3d0d33c515071a1414b6899f3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - clear AES key schedule from stack qat_alg_xts_reverse_key() expands the forward XTS AES key on the stack. That schedule contains key material and can remain in the stack frame. Clear the temporary crypto_aes_ctx with memzero_explicit() after the copy.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.11affected
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before b9cf42622b30178f554fa74411eec67e02d70411affected · git
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before fb1194b78a163cc56bb9480c707fc34b53522359affected · git
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before 892f34dc1819cceb8841005a68086710ce3763b6affected · git
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before dcaa0f1e86cbcb01f68131ae907b54cf299a3592affected · git
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before 9af019e213ada5c3d0d33c515071a1414b6899f3affected · git
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before 92e4979e1a770860b26aa3d90cce0c4c6a53833caffected · git
- 5106dfeaeabea73d5132daab1d89d57b57fa98b7 and later · before d41a9fcfb7f9ee36e4a4aaf5e7996bca6be1e7a9affected · git
- before 5.11not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93159Sep 17, 2026 · crypto: atmel-sha204a - fix heap info leak on I2C transfer failure0Monitor
- ← EarlierCVE-2026-93160Sep 17, 2026 · crypto: atmel-ecc - reject hardware ECDH without a public key0Monitor
- Later →CVE-2026-93162Sep 17, 2026 · crypto: qat - cancel work on re-enable SR-IOV timeout0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 892f34dc1819cceb8841005a68086710ce3763b6 | Vendor (CNA) |
| Linux Linux | 92e4979e1a770860b26aa3d90cce0c4c6a53833c | Vendor (CNA) |
| Linux Linux | 9af019e213ada5c3d0d33c515071a1414b6899f3 | Vendor (CNA) |
| Linux Linux | b9cf42622b30178f554fa74411eec67e02d70411 | Vendor (CNA) |
| Linux Linux | d41a9fcfb7f9ee36e4a4aaf5e7996bca6be1e7a9 | Vendor (CNA) |
| Linux Linux | dcaa0f1e86cbcb01f68131ae907b54cf299a3592 | Vendor (CNA) |
| Linux Linux | fb1194b78a163cc56bb9480c707fc34b53522359 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/92e4979e1a770860b26aa3d90cce0c4c6a53833c
- git.kernel.org/stable/c/9af019e213ada5c3d0d33c515071a1414b6899f3
- git.kernel.org/stable/c/b9cf42622b30178f554fa74411eec67e02d70411
- git.kernel.org/stable/c/d41a9fcfb7f9ee36e4a4aaf5e7996bca6be1e7a9
- git.kernel.org/stable/c/dcaa0f1e86cbcb01f68131ae907b54cf299a3592
- git.kernel.org/stable/c/fb1194b78a163cc56bb9480c707fc34b53522359
Vendor advisories and official records. Exploit/PoC links are deliberately left out.