Strix
73.2K

CVE-2026-98664

UnknownEPSS 0.20%

Last modified

CVE-2026-98664 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.20% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.20%

9.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < 48bb3c9b4a2fac64cb17c357418ebfbd4c9ac8ff; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < 69cc001761894c65a0eef1bb6df911b39d30d71e; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < d32eb2161b452a25b03f915f431bdcb9722cd92c; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < d3078aaef8af4648f94eeafde4b7b36efd9838d1; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < e9b4c00f775a915b759b08bfe2c5e806a8301a59; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < 50e8d70ba0743f88afd7e49f9cebd1841ee677f5; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < f501302ebb9e1504162351b951fe3ae331c852ab; >= ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < d94787287a113a1326211647d5e0deed1e9de105
LinuxLinux5.8

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98664?
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.
How severe is CVE-2026-98664?
Severity scoring for CVE-2026-98664 is pending analysis. The EPSS model estimates a 0.20% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98664?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98664?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST