Look up another CVE · open CVE-2024-42156 in the interactive tracker
CVE-2024-42156
s390/pkey: Wipe copies of clear-key structures on failure
Published 2024-07-30 (2 years ago) by the Linux kernel CNA. Subsystem drivers/s390. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2024-42156 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.9.9-1 | Update the kernel and reboot. Fixed in 6.9.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.9.9-1 | Update the kernel and reboot. Fixed in 6.9.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.9.9-1 | Update the kernel and reboot. Fixed in 6.9.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Wipe all sensitive data from stack for all IOCTLs, which convert a clear-key into a protected- or secure-key.
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/pkey_api.c
- What this is
- S390 ZCRYPT AND PKEY DRIVER AND AP BUSMAINTAINERS section matched on drivers/s390/crypto/ · linux-s390@vger.kernel.org · Supported
Check it on the machine
grep -wE 'CONFIG_PKEY|CONFIG_S390' /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.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_PKEY, CONFIG_S390
- 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
- 2024-07-30 (2 years ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.21%, higher than 10.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 5.4 | 6.6.64 | a891938947f4 |
| 5.4 | 6.9.9 | 7f6243edd901 |
| 5.4 | 6.10 | d65d76a44ffe |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2024-42156, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.