Key-material exposure via failed userspace copy
Published Jul 30, 2024 · Updated May 11, 2026
Information disclosure in the Linux s390 protected-key API allows local users to expose cryptographic key material retained on the kernel stack. In pkey_unlocked_ioctl, failed copy_to_user calls for PKEY_CLR2SECK and PKEY_CLR2PROTK return before memzero_explicit erases the kcs or kcp structure. Exploitation requires high-privileged local access on an s390 system and a failed userspace copy; the reported consequence is limited to confidentiality.
Summary
What happened
Information disclosure in the Linux s390 protected-key API allows local users to expose cryptographic key material retained on the kernel stack. In pkey_unlocked_ioctl, failed copy_to_user calls for PKEY_CLR2SECK and PKEY_CLR2PROTK return before memzero_explicit erases the kcs or kcp structure. Exploitation requires high-privileged local access on an s390 system and a failed userspace copy; the reported consequence is limited to confidentiality.
The record
- CVE
- CVE-2024-42157
- Published
- Jul 30, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.11
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <1d8c270de5eb74245d72325d285894a577a945d9
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <4889f117755b2f18c23045a0f57977f3ec130581
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <6e2e374403bf73140d0efc9541cb1b3bea55ac02
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <90a01aefb84b09ccb6024d75d85bb8f620bd3487
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <93c034c4314bc4c4450a3869cd5da298502346ad
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <b5eb9176ebd4697bc248bf8d145e66d782cf5250
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <c44a2151e5d21c66b070a056c26471f30719b575
- Affected versionversion=e80d4af0a320972aac58e2004d0ba4e44ef4c5c7 <c51795885c801b6b7e976717e0d6d45b1e5be0f0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo