Live › vulnerability › CVE-2026-98664
Go to dashboardIn the Linux IIO driver for the ADIS16400 IMU, the serial_number debugfs file is not protected against unbind, so a read in progress can access memory freed when the device is unbound. The sources do not describe a specific attacker outcome beyond this use-after-free.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the IIO adis16400 IMU driver loaded, where the device can be unbound while debugfs is being read. Systems without this hardware or driver are unlikely to be affected. The sources do not say more.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98664")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.