Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can make certain IBM s390/s390x systems using Btrfs zlib compression crash when the compression path reads beyond the intended input range. The public record shows a kernel BUG and panic on a debug kernel. The business risk is availability disruption, not a confirmed data breach or remote takeover.
Executive priority
Schedule remediation for affected s390/s390x Btrfs systems through normal kernel update channels. Escalate if these hosts support critical workloads or have recent matching kernel panics. There is no provided evidence of active exploitation.
Technical view
The flaw is in the Btrfs zlib compression path for s390 hardware acceleration. strm.avail_in could be rounded to a page-size multiple even when the actual input length was shorter, causing reads past the supplied range and triggering a btrfs_compress_folios assertion and kernel panic in the reported debug build.
Likely exposure
Exposure appears limited to Linux systems on s390/s390x using Btrfs with zlib compression and the affected kernel code path. The source marks Linux 6.12 and 6.13-related versions as affected, but does not provide broad distro package mapping.
Exploitation context
CISA KEV is false in the provided bundle, and no cited source reports active exploitation. The public evidence is a kernel crash trace during Btrfs delayed allocation work. Practical exploitability and non-debug-kernel impact are not fully described in the sources.
Researcher notes
The source is kernel-resolution text, not a full exploitability analysis. It identifies an input length accounting bug in zlib_compress_folios on the s390 hardware acceleration path and references two stable commits. CVSS, CWE, and distro-level fixed versions are absent.
Mitigation direction
Apply vendor kernel updates containing the referenced stable kernel fixes.
Prioritize affected s390/s390x hosts using Btrfs compression.
Check distribution advisories for exact fixed package versions.
Avoid inventing workarounds; follow kernel or distro vendor guidance.
Treat unexplained kernel panics on matching hosts as operationally relevant.
Validation and detection
Inventory Linux s390/s390x systems and running kernel versions.
Identify hosts using Btrfs with zlib compression enabled.
Confirm whether vendor kernels include the referenced stable commits.
Review kernel logs for btrfs_compress_folios assertions or panic traces.
Track distro advisories because affected package mapping is incomplete here.
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-57923 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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jan 19, 2025, 11:52 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.