Look up another CVE · open CVE-2026-80546 in the interactive tracker
CVE-2026-80546
s390/zcrypt: Improve CCA CPRB length and overflow checks
Published 2026-08-26 (2 months ago) by the Linux kernel CNA. Subsystem drivers/s390. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80546 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The xcrb_msg_to_type6cprb_msgx() function lacks proper input validation, creating security vulnerabilities: 1. Integer overflow after CEIL4 alignment: Signed int variables could overflow during 4-byte boundary alignment, causing undersized buffer allocations or incorrect bounds checking. 2. Missing minimum size validation: The CPRBX structure is copied from userspace without verifying sufficient buffer length. Undersized buffers cause uninitialized memory access when reading structure fields like cprbx.cprb_len and cprbx.domain. 3. Arithmetic overflow in sum calculations: Adding control block and data block sizes could overflow, bypassing size checks and enabling buffer overflows. Fix by using size_t for length calculations, adding U32_MAX boundary checks after alignment, validating minimum control block size before copying from userspace, and detecting sum calculation overflows.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/s390/crypto/zcrypt_msgtype6.c
- What this is
- S390 ZCRYPT AND PKEY DRIVER AND AP BUSMAINTAINERS section matched on drivers/s390/crypto/ · linux-s390@vger.kernel.org · Supported
- Kernel module
- zcrypt
Check it on the machine
grep -wE 'CONFIG_S390|CONFIG_ZCRYPT' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w zcryptPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian does not build this code in 1 release. It does build it in 3 releases, so the answer depends on which release the machine runs.
- bookwormn
- trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64
- forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64
- n
- not enabled on any flavour - this release does not build the code
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_S390, CONFIG_ZCRYPT
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-26 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.19%, higher than 8.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/s390
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.18.57 | 6.18.57 | 584400144020 |
| 7.1 | 7.1.10 | 50fe5133dcb4 |
| 7.1 | 7.2 | 35ac6754ba6d |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is in xcrb_msg_to_type6cprb_msgx(), reached only from the ZSECSENDCPRB ioctl on the s390 zcrypt character device (zcrypt_unlocked_ioctl -> zsecsendcprb_ioctl -> _zcrypt_send_cprb -> prep_cca_ap_msg); there is no network, adjacent-radio, or physical-bus entry point.
- AC:LAttack complexity, low
- An attacker with a zcrypt fd fully controls the ica_xcRB length fields and CPRB buffers and can craft values that bypass flawed CEIL4/sum checks on every ioctl; no race, timing dependency, or uncontrolled memory layout is required.
- PR:LPrivileges required, low
- Exploitation needs only local access to a zcrypt device node with ZSECSENDCPRB permitted via zcrypt_check_ioctl(); on IBM Z/LinuxONE admins routinely delegate such access to non-root crypto service accounts through custom zcdn nodes, not init-namespace root alone.
- UI:NUser interaction, none
- The attacker triggers the flaw directly by issuing ZSECSENDCPRB with a crafted ica_xcRB from their own process; no separate victim action such as mounting a filesystem or opening a file is required.
- S:UScope, unchanged
- Impact is heap corruption and kernel memory disclosure within the host kernel address space during AP message preparation; it does not cross a VM, IOMMU, or other changed security-authority boundary.
- C:HConfidentiality impact, high
- Undersized request_control_blk_length copies fewer than sizeof(CPRBX) bytes yet the code reads cprbx.cprb_len and cprbx.domain from uninitialized kmalloc memory; integer-overflow bypasses can also yield out-of-bounds reads beyond the allocated ap_msg buffer.
- I:HIntegrity impact, high
- Signed-int CEIL4 alignment and sum overflows can make ap_msg->len smaller than copied data and place req_data before the kmalloc buffer, enabling z_copy_from_user() heap buffer overflows and attacker-influenced memory corruption suitable for control-flow hijack.
- A:HAvailability impact, high
- Heap underflow/overflow and corrupted AP message buffers can immediately oops or panic the kernel; prep_cca_ap_msg runs before any crypto hardware is required, so the crash primitive is repeatable from ioctl alone.