CVE-2024-42320: s390/dasd: fix error checks in dasd_copy_pair_store()
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: fix error checks in dasd_copy_pair_store()
dasd_add_busid() can return an error via ERR_PTR() if an allocation
fails. However, two callsites in dasd_copy_pair_store() do not check
the result, potentially resulting in a NULL pointer dereference. Fix
this by checking the result with IS_ERR() and returning the error up
the stack.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in the IBM s390 DASD storage driver. An allocation failure may be handled incorrectly, causing a kernel NULL pointer dereference. Business impact is most likely service disruption on affected Linux systems using this specialized mainframe storage path, not broad internet compromise.
Executive priority
Treat this as targeted operational risk for mainframe Linux environments. It is not supported as actively exploited, but affected storage hosts should be patched through normal kernel maintenance because a kernel crash can interrupt critical workloads.
Technical view
dasd_add_busid() may return ERR_PTR() on allocation failure. dasd_copy_pair_store() had two callsites that did not check that result, creating a potential NULL pointer dereference. The upstream resolution adds IS_ERR() checks and returns the error up the stack.
Likely exposure
Exposure appears limited to Linux on s390 systems using the DASD driver and the affected copy-pair code path. The provided record lists affected Linux kernel entries including 6.1, 6.1.103, 6.6.44, 6.10.3, and 6.11, but product-specific packaging status requires vendor confirmation.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The described failure depends on an allocation-error path in a kernel storage driver. No public exploitability details, required privileges, or remote attack path are established in the provided evidence.
Researcher notes
The record lacks CVSS, CWE, privilege, and trigger details. Analysis should stay close to the upstream fix: unchecked ERR_PTR handling in dasd_copy_pair_store(). Validate exposure through kernel source/package lineage and s390 DASD usage, not generic Linux presence alone.
Mitigation direction
Apply a vendor-supported kernel containing the referenced stable fixes.
For Debian LTS systems, review the cited January 2025 advisory.
Prioritize s390 hosts using DASD storage features.
Check Linux distribution advisories for exact fixed package versions.
Avoid direct wrangler-style assumptions; follow kernel or distribution guidance only.
Validation and detection
Inventory Linux s390 or s390x systems using DASD storage.
Compare running kernel packages against vendor fixed versions.
Confirm the relevant stable commit is included in deployed kernels.
Review logs for unexplained kernel oops or storage-driver crashes.
Document affected, fixed, and exception systems separately.
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-42320 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.