iio: gyro: adis16136: fix unprotected debugfs reads
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9aaea09b4cbdbe1a80ab3fa1a5d32c3ec61fa6e2 · < b53dc6e15aead039bc6a5e08060c96786240c81d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iio: gyro: adis16136: fix unprotected debugfs reads
The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.
Use debugfs_create_file() instead.
From the CVE record · Linux
The Linux kernel’s adis16136 gyro driver has an unprotected debugfs serial_number read. If a read is in progress during device unbind, the device can be freed while the read still uses it. This requires a debugfs read and a concurrent unbind; the input does not specify authentication requirements.
Engineers running Linux kernels with the adis16136 gyro driver should check whether their kernel includes the fix; affected versions are not specified.