CVE-2024-57912
Linux Kernel 4.9 – 6.1.125
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-57912 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-57912 is an information disclosure vulnerability in the Linux kernel's Industrial I/O (IIO) subsystem, specifically the zpa2326 pressure sensor driver. The issue arises in the triggered buffer functionality, where a local 'sample' struct used to push data to userspace contains an uninitialized memory hole between the u16 temperature field and the u64 timestamp field. This hole, consisting of padding bytes, is never zeroed out before transmission, potentially leaking uninitialized kernel memory to userspace applications.
A local attacker with low privileges can exploit this vulnerability with low complexity and no user interaction required. Successful exploitation allows reading of sensitive uninitialized kernel data, as indicated by the CVSS v3.1 base score of 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H). The confidentiality impact is high due to the information leak, while the availability impact is also rated high, though the root cause stems from the uninitialized resource (CWE-908).
Mitigation is provided through upstream kernel patches, available in multiple stable branches via the referenced commits: 6007d10c5262f6f71479627c1216899ea7f09073, 64a989aa7475b8e76e69b9ec86819ea293e53bab, 9629ff1a86823269b12fb1ba9ca4efa945906287, 979a0db76ceda8fe1f2f85a116bfe97620ebbadf, and b7849f62e61242e0e02c776e1109eb81e59c567c. These patches initialize the 'sample' struct to zero before use, preventing the leak. Security practitioners should apply the relevant stable kernel updates to affected systems using the zpa2326 driver.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53815
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: iio: pressure: zpa2326: fix information leak in triggered buffer The 'sample' local struct is used to push data to user space from a triggered buffer, but it has a hole…
more
between the temperature and the timestamp (u32 pressure, u16 temperature, GAP, u64 timestamp). This hole is never initialized. Initialize the struct to zero before using it to avoid pushing uninitialized information to userspace.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.
Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.
Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.
Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.
Application security requirements can specify mandatory initialization of variables and resources before use.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.