CVE-2026-99494: Linux kernel · s390/zcrypt: Fix out-of-bounds ptr advance in cca_query_crypto_facility()
Source GCVE Database
Not known to be exploited · fixed in bd30e2b60e811140861d53030cf9b6226b46c032 : patch Linux kernel soon.
Data as of 19 Nov 2026, 17:19 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in bd30e2b60e811140861d53030cf9b6226b46c032, 21268907891d5496e495ca17511aff11d8f99731, 49dfd61f1c2ddfe028d4a9a603afc33b013e9ee9 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
Upgrade Linux kernel to bd30e2b60e811140861d53030cf9b6226b46c032, 21268907891d5496e495ca17511aff11d8f99731, 49dfd61f1c2ddfe028d4a9a603afc33b013e9ee9 or 9fd7fca66735307fd7afa3450882a55ef80f2add.
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– |
AI-suggested
A fix has been implemented that adds validation of length fields against the remaining reply buffer space before pointer advancement. Users should apply the official Linux kernel update that includes this fix once available.
Description
A vulnerability in the Linux kernel's s390/zcrypt component allowed an out-of-bounds pointer advance in the cca_query_crypto_facility() function. This occurred because the code advanced a pointer based on a length value from hardware without verifying it stayed within the allocated buffer, potentially leading to out-of-bounds memory access or kernel memory exposure. The issue has been fixed by adding checks to validate the length fields before pointer advancement.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99494 (opens in a new tab)
- git.kernel.org/stable/c/21268907891d5496e495ca17511aff11d8f99731 (opens in a new tab)
- git.kernel.org/stable/c/49dfd61f1c2ddfe028d4a9a603afc33b013e9ee9 (opens in a new tab)
- git.kernel.org/stable/c/9fd7fca66735307fd7afa3450882a55ef80f2add (opens in a new tab)
- git.kernel.org/stable/c/bd30e2b60e811140861d53030cf9b6226b46c032 (opens in a new tab)