CVE-2024-57908
Linux Kernel 4.0 – 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-57908 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 12th 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-57908 is an information disclosure vulnerability in the Linux kernel's Industrial I/O (IIO) subsystem, specifically the kmx61 inertial measurement unit (IMU) driver. The issue arises in the triggered buffer handling where a local 'buffer' array is used to push data to userspace. This array is not fully initialized, as the code only assigns values via iio_for_each_active_channel(), leaving values for inactive channels uninitialized. As a result, uninitialized kernel stack memory can be leaked to userspace. The vulnerability is rated with 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 associated with CWE-908 (Use of Uninitialized Resource).
A local attacker with low privileges can exploit this vulnerability by interacting with the kmx61 driver through the IIO interface, such as by setting up a triggered buffer and reading the output. Successful exploitation allows disclosure of sensitive uninitialized kernel memory to userspace, potentially exposing kernel internals that could aid in further attacks. The CVSS metrics indicate high confidentiality impact from the leak, with high availability impact possibly stemming from related mishandling, though the primary effect is the information disclosure.
Mitigation is provided through upstream Linux kernel patches available in stable releases, as documented in the referenced commits. These patches initialize the 'buffer' array to zero before use, ensuring that inactive channels do not leak uninitialized data. Security practitioners should apply the relevant stable kernel updates, such as those at https://git.kernel.org/stable/c/0871eb8d700b33dd7fa86c80630d62ddaef58c2c and similar commits, to affected systems using the kmx61 driver.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53811
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: iio: imu: kmx61: fix information leak in triggered buffer The 'buffer' local array is used to push data to user space from a triggered buffer, but it does not set…
more
values for inactive channels, as it only uses iio_for_each_active_channel() to assign new values. Initialize the array 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.