CVE-2024-57908: iio: imu: kmx61: fix information leak in triggered buffer
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 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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-57908 is a Linux kernel issue in the KMX61 IMU sensor driver. A local user who can access the relevant sensor buffer may receive uninitialized kernel memory in user space. The business risk is mainly data exposure on systems with this hardware or driver enabled.
Executive priority
Prioritize patching for laptops, embedded devices, industrial systems, or shared Linux hosts with motion-sensor hardware. Risk is narrower than internet-facing vulnerabilities, but kernel memory disclosure can support broader compromise chains.
Technical view
The kmx61 Industrial I/O triggered buffer filled only active channels, leaving inactive channel slots uninitialized before pushing the buffer to user space. The kernel fix zero-initializes the local array before use. CVSS 3.1 is 7.1, with local access and low privileges required.
Likely exposure
Exposure is likely limited to Linux systems using or loading the kmx61 IIO IMU driver and allowing local users to read triggered buffers. Distribution kernels may differ due to backports, so package-level vendor status matters.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. The CVSS vector indicates local, low-privilege exploitation without user interaction. No remote attack path is supported by the source bundle.
Researcher notes
Focus validation on driver reachability, IIO triggered-buffer access, and vendor backport status. The source bundle names the root cause and fix pattern but does not provide exploit evidence or complete distribution-specific affected ranges.
Mitigation direction
Update to a vendor kernel containing the kmx61 buffer initialization fix.
Use distribution security advisories, including Debian LTS notices where applicable.
Disable or unload the kmx61 driver if unused and operationally safe.
Restrict local access to affected sensor interfaces where feasible.
Validation and detection
Inventory Linux kernels and identify systems with the kmx61 driver present or loaded.
Confirm whether vendor packages include one of the referenced stable fixes.
Check Debian LTS advisory applicability for Debian-based affected systems.
Review IIO device permissions for unnecessary local user access.
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.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.