CVE-2024-42158: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings
In the Linux kernel, the following vulnerability has been resolved:
s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings
Replace memzero_explicit() and kfree() with kfree_sensitive() to fix
warnings reported by Coccinelle:
WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1506)
WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1643)
WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1770)
Security readout for executives and security teams
Plain-English summary
This Linux kernel CVE concerns safer cleanup of sensitive memory in the s390 protected key code. The fix replaces manual zeroing plus free with kfree_sensitive(). The sources do not provide CVSS, CWE, impact details, or evidence of active exploitation, so urgency should be based on whether the organization runs affected s390 Linux kernels.
Executive priority
Treat this as targeted kernel maintenance, not an emergency, unless critical s390 systems rely on protected key handling. The available evidence does not show exploitation or quantified severity, but sensitive-memory cleanup in kernel cryptographic code is worth tracking through normal patch governance.
Technical view
The resolved issue is in Linux kernel s390/pkey code. Coccinelle reported opportunities to use kfree_sensitive() at three locations, replacing memzero_explicit() followed by kfree(). This suggests a sensitive-memory cleanup hardening change, but the source bundle does not document a concrete attack path, privilege requirement, or data exposure scenario.
Likely exposure
Exposure appears limited to Linux systems using the s390 architecture and pkey functionality. The record lists Linux kernel ranges as affected, but the supplied version data is not detailed enough to safely restate exact fixed or vulnerable ranges beyond the referenced stable commits.
Exploitation context
No active exploitation is supported by the supplied sources. The CVE is not marked KEV, and the references only show kernel stable fixes. There is no public exploit status, attacker model, or weaponized technique in the provided bundle.
Researcher notes
The record is unusually sparse: no CVSS, CWE, exploitability analysis, or explicit impact is provided. Analysis should stay close to the commit rationale: replacing memzero_explicit()+kfree() with kfree_sensitive() in s390/pkey after Coccinelle warnings.
Mitigation direction
Check kernel vendor advisories for CVE-2024-42158 applicability.
Update affected s390 Linux kernels to builds containing the referenced stable fixes.
Prioritize systems using protected key or cryptographic key management features.
If no vendor package is available, request vendor guidance before backporting.
Validation and detection
Inventory Linux kernel versions on IBM s390 systems.
Confirm whether s390 pkey functionality is enabled or in use.
Verify kernel packages include the referenced stable commits.
Document non-s390 systems as not indicated by these sources.
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-42158 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.