iio: dummy: iio_simply_dummy_buffer: fix information leak in triggered buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 415f792447572ef1949a3cef5119bbce8cc66373 · < ea703cda36da0dacb9a2fd876370003197d8a019| No fix yet |
| Linux Linux |
|
|
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, 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.
From the CVE record · Linux
The Linux kernel’s IIO dummy triggered buffer leaves inactive channel values uninitialized before pushing data to user space. A local user reading the buffer may receive uninitialized information; the input does not specify authentication requirements or whether other user interaction is needed.
Anyone running a Linux kernel with the affected IIO dummy triggered buffer should check their kernel version; affected versions are not specified.