Javier Carrasco

The issue concerns an information leak in the triggered buffer of the Linux kernel's ti-ads1119 ADC driver. The `scan` local struct, used to push data to user space, contains an uninitialized hole between the sample and the timestamp. This hole is never initialized, allowing uninitialized information to be pushed to userspace. The fix involves initializing the struct to zero before using it.

The issue concerns an information leak in the triggered buffer of the ti-ads8688 driver in the Linux kernel. 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. This can lead to pushing uninitialized information to userspace. The array needs to be initialized to zero before use to avoid this issue.

The issue concerns an information leak in the triggered buffer of the Rockchip SARADC driver in the Linux kernel. The 'data' local struct 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. This can lead to pushing uninitialized information to userspace. The struct needs to be initialized to zero before using it to avoid this issue.

The issue concerns an information leak in the triggered buffer of the Linux kernel's iio: imu: kmx61 module. The 'buffer' local array is used to push data to user space from a triggered buffer but does not set values for inactive channels, as it only uses `iio for each active channel()` to assign new values. This can lead to pushing uninitialized information to userspace. The array needs to be initialized to zero before use to avoid this issue.

The issue concerns an information leak in the triggered buffer of the Linux kernel's iio light bh1745 component. The local struct 'scan' is used to send data to user space from a triggered buffer but does not initialize values for inactive channels, as it only uses `iio for each active channel()` to assign new values. This can lead to sending uninitialized information to user space. The struct should be initialized to zero before use to prevent this leak.

The issue concerns an information leak in the triggered buffer of the Linux kernel's iio: light: vcnl4035 driver. The 'buffer' local array is used to push data to userspace from a triggered buffer but does not set an initial value for the single data element, which is an u16 aligned to 8 bytes. This leaves at least 4 bytes uninitialized even after writing an integer value with regmap read(). Initializing the array to zero before using it avoids pushing uninitialized information to userspace.

The issue concerns an information leak in the Linux kernel's iio:dummy buffer. Specifically, the `data` array is allocated via `kmalloc()` and used to push data to user space from a triggered buffer. However, it does not set values for inactive channels, as it only uses `iio for each active channel()` to assign new values. This can lead to sending uninitialized information to user space. To avoid this, `kzalloc` should be used for memory allocation.

A vulnerability has been resolved in the Linux kernel. The issue is related to the `iio: pressure: zpa2326` component, where the local `sample` struct is used to push data to user space from a triggered buffer. However, this struct has a hole between the temperature and the timestamp, which is never initialized. This could lead to sending uninitialized information to user space. The struct should be initialized to zero before use to avoid this issue.