CVE-2024-57911
Linux Kernel 4.5 – 5.4.290
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). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-57911 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Linux Kernel. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); 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-57911 is an information disclosure vulnerability in the Linux kernel's Industrial I/O (IIO) subsystem, specifically affecting the dummy driver's iio_simply_dummy_buffer component. The flaw occurs because the 'data' array is allocated using kmalloc() to push data from a triggered buffer to userspace, but it only assigns values to active channels via iio_for_each_active_channel(), leaving inactive channels uninitialized. This can result in uninitialized kernel memory being exposed to userspace. The vulnerability carries a CVSS v3.1 base score of 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) and is classified under CWE-908 (Use of Uninitialized Resource).
A local attacker with low privileges (PR:L) can exploit this vulnerability by accessing the affected IIO dummy triggered buffer. Exploitation requires local access and low complexity with no user interaction. Successful attacks enable high confidentiality impact through leakage of uninitialized data and high availability impact, within an unchanged security scope.
Mitigation involves applying upstream kernel patches that replace kmalloc() with kzalloc() for the 'data' array allocation, ensuring zero-initialization of inactive channels. Relevant stable branch commits include: https://git.kernel.org/stable/c/006073761888a632c5d6f93e47c41760fa627f77, https://git.kernel.org/stable/c/03fa47621bf8fcbf5994c5716021527853f9af3d, https://git.kernel.org/stable/c/333be433ee908a53f283beb95585dfc14c8ffb46, https://git.kernel.org/stable/c/74058395b2c63c8a438cf199d09094b640f8c7f4, and https://git.kernel.org/stable/c/b0642d9c871aea1f28eb02cd84d60434df594f67.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53814
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer The 'data' array is allocated via kmalloc() and it is used to push data to user space from a triggered buffer,…
more
but it does not set values for inactive channels, as it only uses iio_for_each_active_channel() to assign new values. Use kzalloc for the memory allocation 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 coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.