CVE-2026-80543: Linux kernel · s390/zcrypt: Pad trailing CCA or EP11 message with zeros
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 12 Nov 2026, 20:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 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 12 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinux-aws-6.17pkg:deb/ubuntu/linux-aws-6.17?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinux-azure-6.14pkg:deb/ubuntu/linux-azure-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinux-azure-6.17pkg:deb/ubuntu/linux-azure-6.17?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinux-azure-fde-6.14pkg:deb/ubuntu/linux-azure-fde-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch has been applied to pad trailing bytes with zeros, preventing kernel memory exposure. Users should update to the fixed Linux kernel versions listed to remediate this issue.
Description
A vulnerability in the Linux kernel s390/zcrypt subsystem caused uninitialized kernel memory (up to 3 bytes) to be included in messages sent to crypto card firmware. This occurred because the message length was adjusted to a 4-byte boundary after copying from user space, leaving a gap of uninitialized bytes. The issue was fixed by padding these trailing bytes with zeros to prevent unintended kernel memory exposure.