CVE-2026-98664 iio: imu: adis16400: fix unprotected debugfs reads
A use-after-free vulnerability in the Linux kernel adis16400 driver allows local attackers to cause a denial of service or potentially execute code via unprotected debugfs reads.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-98664?
CVE-2026-98664 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-98664?
How do I fix CVE-2026-98664?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-98664 being exploited?
There is no known exploitation of CVE-2026-98664 in the wild and no public exploit code.
Sources
Also known as AZL-109127, BELL-CVE-2026-98664, DEBIAN-CVE-2026-98664, GHSA-w4fg-xq8w-gq57, UBUNTU-CVE-2026-98664.