The flaw arises from a stack‑allocated iio_buff structure that is declared without initialization, allowing a local user to read uninitialized memory through the tagged FIFO path. Up to 6 bytes plus surrounding padding that precede the timestamp are leaked when the buffer is copied to userspace, exposing kernel memory contents. This weakness is represented by CWE‑908 and results in information disclosure; it does not provide privilege escalation or code execution capabilities.

Any Linux kernel build that ships a version of the st_lsm6dsx IIO driver before the commit that zero‑initializes the buffer is affected. The issue existed in both stable and development kernels up through the date of the patch. Kernel images that include commit c14edb4d0bdc or its equivalent fix are considered safe.

The EPSS metric is reported as <1 %, and the vulnerability is not listed in the CISA KEV catalog, indicating a very low probability of exploitation. Based on the description, the likely attack vector is local, requiring access to the IMU device interface (e.g., /dev/iio:deviceX), which is normally restricted to privileged users. Consequently, the immediate risk to typical unprivileged users is minimal though a local information disclosure is still possible in environments that expose the IMU to untrusted processes.