LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42156: s390/pkey: Wipe copies of clear-key structures on failure

In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe copies of clear-key structures on failure Wipe all sensitive data from stack for all IOCTLs, which convert a clear-key into a protected- or secure-key.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux kernel issue in IBM Z/s390 protected-key handling could leave copies of clear-key material in memory after failed conversion operations. The record does not provide CVSS, CWE, or evidence of active exploitation.

Executive priority

Track and patch during normal kernel maintenance unless your business runs sensitive key operations on IBM Z/s390 Linux. For those environments, prioritize validation because the issue concerns clear-key material handling.

Technical view

The s390 pkey code handles IOCTLs that convert clear-key structures into protected or secure keys. On failure, stack copies of sensitive clear-key structures were not fully wiped. Kernel stable commits address this by clearing sensitive stack data for those IOCTL paths.

Likely exposure

Exposure appears limited to Linux systems on s390 architecture using the pkey functionality for clear-key conversion. The source bundle identifies Linux kernel versions and stable fixes, but does not provide distro package status or broader product mapping.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit activity, or practical attack prerequisites. Treat this as sensitive-data exposure risk pending vendor-specific analysis.

Researcher notes

Evidence is narrow: the CVE description and kernel references describe a failure-path cleanup issue, not a disclosed exploit primitive. No CVSS, CWE, or exploitability detail is provided in the source bundle.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check your Linux distribution security advisories for backported patches.
  • Prioritize IBM Z/s390 systems using pkey clear-key conversion.
  • Avoid assuming non-s390 Linux systems are affected without vendor confirmation.

Validation and detection

  • Inventory Linux kernels running on s390 infrastructure.
  • Confirm whether the referenced stable commits or distro backports are present.
  • Identify workloads using pkey IOCTL clear-key conversion paths.
  • Review vendor advisories for affected package versions and remediation status.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42156 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf2bbc96e7cfad3891b7bf9bd3e566b9b7ab4553d, f2bbc96e7cfad3891b7bf9bd3e566b9b7ab4553d, f2bbc96e7cfad3891b7bf9bd3e566b9b7ab4553dunaffected
LinuxLinux5.4, 0, 6.6.64, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.