Skip to main content
VulnerabilityPublished Updated

CVE-2026-98664: Linux kernel · iio: imu: adis16400: fix unprotected debugfs reads

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f501302ebb9e1504162351b951fe3ae331c852ab : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f501302ebb9e1504162351b951fe3ae331c852ab, e9b4c00f775a915b759b08bfe2c5e806a8301a59, d94787287a113a1326211647d5e0deed1e9de105 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < f501302ebb9e1504162351b951fe3ae331c852ab
Fixed in
  • f501302ebb9e1504162351b951fe3ae331c852ab
LinuxLinuxAffected
  • ≥ ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < e9b4c00f775a915b759b08bfe2c5e806a8301a59
Fixed in
  • e9b4c00f775a915b759b08bfe2c5e806a8301a59
LinuxLinuxAffected
  • ≥ ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < d94787287a113a1326211647d5e0deed1e9de105
Fixed in
  • d94787287a113a1326211647d5e0deed1e9de105
LinuxLinuxAffected
  • ≥ ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < d3078aaef8af4648f94eeafde4b7b36efd9838d1
Fixed in
  • d3078aaef8af4648f94eeafde4b7b36efd9838d1
LinuxLinuxAffected
  • ≥ ae1d37a9bb4bd8d9091a40d153143e99b115ee37, < 50e8d70ba0743f88afd7e49f9cebd1841ee677f5
Fixed in
  • 50e8d70ba0743f88afd7e49f9cebd1841ee677f5
LinuxLinuxAffected
  • =5.8
Fixed in–

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.

References

Community reviews

Loading reviews…