Skip to main content

CVE-2023-52733: Vulnerability in Linux Linux

High
VulnerabilityCVE-2023-52733cvecve-2023-52733
Published: Tue May 21 2024 (05/21/2024, 15:22:58 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: s390/decompressor: specify __decompress() buf len to avoid overflow Historically calls to __decompress() didn't specify "out_len" parameter on many architectures including s390, expecting that no writes beyond uncompressed kernel image are performed. This has changed since commit 2aa14b1ab2c4 ("zstd: import usptream v1.5.2") which includes zstd library commit 6a7ede3dfccb ("Reduce size of dctx by reutilizing dst buffer (#2751)"). Now zstd decompression code might store literal buffer in the unwritten portion of the destination buffer. Since "out_len" is not set, it is considered to be unlimited and hence free to use for optimization needs. On s390 this might corrupt initrd or ipl report which are often placed right after the decompressor buffer. Luckily the size of uncompressed kernel image is already known to the decompressor, so to avoid the problem simply specify it in the "out_len" parameter.

AI-Powered Analysis

AILast updated: 07/09/2025, 00:12:36 UTC

Technical Analysis

CVE-2023-52733 is a high-severity vulnerability in the Linux kernel affecting the s390 architecture's decompression routine. The issue arises from the __decompress() function, which historically did not specify the output buffer length parameter (out_len) when decompressing the kernel image using the zstd compression library. This omission was previously safe because the decompression code assumed no writes would occur beyond the uncompressed kernel image boundary. However, a change introduced in commit 2aa14b1ab2c4, which updated the zstd library to version 1.5.2, altered the decompression behavior. The updated zstd code may store literal buffers in the unwritten portion of the destination buffer. Since out_len was unspecified and thus treated as unlimited, this can lead to buffer overflow, potentially corrupting adjacent memory regions such as the initial RAM disk (initrd) or the Initial Program Load (IPL) report, which are often located immediately after the decompressor buffer on s390 systems. The vulnerability is classified under CWE-120 (Buffer Copy without Checking Size of Input) and affects Linux kernel versions containing the specified commit. The flaw impacts confidentiality, integrity, and availability as it can corrupt critical boot components, potentially leading to system instability or compromise. The vulnerability requires local privileges (AV:L), low attack complexity (AC:L), and privileges (PR:L) but no user interaction (UI:N). No known exploits are currently reported in the wild. The fix involves specifying the correct output buffer length to the __decompress() function to prevent overflow by bounding writes within the allocated buffer size.

Potential Impact

For European organizations running Linux on s390 architecture systems, particularly in enterprise or data center environments, this vulnerability poses a significant risk. The s390 architecture is primarily used in IBM mainframe environments, which are common in financial institutions, government agencies, and large enterprises across Europe. Exploitation could lead to corruption of critical boot components, causing system crashes, denial of service, or potentially enabling privilege escalation or code execution if attackers can manipulate the corrupted memory regions. This could disrupt critical services, lead to data loss, or compromise system integrity. Given the high confidentiality, integrity, and availability impact, organizations relying on affected Linux kernel versions on s390 hardware must prioritize remediation to maintain operational continuity and security compliance.

Mitigation Recommendations

1. Immediate application of the official Linux kernel patches that specify the output buffer length in the __decompress() function is essential. Monitor Linux kernel mailing lists and vendor advisories for updated kernel releases addressing CVE-2023-52733. 2. For organizations unable to patch immediately, implement strict access controls to limit local user privileges on s390 systems, reducing the risk of exploitation by unprivileged users. 3. Conduct thorough integrity checks of boot components (initrd, IPL reports) to detect any corruption or tampering. 4. Employ kernel integrity monitoring tools and runtime protection mechanisms to detect anomalous behavior during boot or decompression phases. 5. Review and harden system boot processes and ensure secure boot mechanisms are enabled to prevent unauthorized modifications. 6. Maintain comprehensive backups of critical system images and configurations to enable rapid recovery in case of corruption or compromise. 7. Engage with hardware and Linux distribution vendors to obtain guidance and support for patch deployment and system validation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-05-21T15:19:24.232Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9830c4522896dcbe73f1

Added to database: 5/21/2025, 9:09:04 AM

Last enriched: 7/9/2025, 12:12:36 AM

Last updated: 8/16/2025, 12:33:41 AM

Views: 19

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats