Live › vulnerability › CVE-2026-98663
Go to dashboardIn the Linux IIO adis16480 IMU driver, the firmware_revision and firmware_date debugfs files are read without the protection debugfs requires, so a read in progress can run after the device is freed on unbind. The sources describe a use-after-free on the kernel side; they do not state what an attacker can gain from it.
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 adis16480 IIO driver, typically hosts with an ADIS16480-family IMU attached. The sources do not say whether a read can be triggered by an unprivileged user, and debugfs is normally only mounted and readable by root. Systems without this hardware or driver can skip it.
No product ranges from the sources yet.
uname -r to see the running kernel versionlsmod | grep adis16480Each 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: adis16480: fix unprotected debugfs reads
The firmware_revision and firmware_date 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98663")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.