iio: imu: adis16400: fix unprotected debugfs reads
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae1d37a9bb4bd8d9091a40d153143e99b115ee37 · < 50e8d70ba0743f88afd7e49f9cebd1841ee677f5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iio: imu: adis16400: fix unprotected debugfs reads
adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.
Commit ae1d37a9bb4b ("iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().
serial_number prints three registers as "%.4x-%.4x-%.4x" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.
From the CVE record · Linux
The Linux kernel's adis16400 serial_number debugfs file does not protect reads while the device is being unbound. A local reader could access a freed device if a read overlaps unbinding; the input does not specify whether authentication is required beyond access to the file.
Engineers running Linux kernels with the adis16400 driver should check whether their kernel includes the fix; affected versions are not specified.