CVE-2026-98663: Linux kernel · iio: imu: adis16480: fix unprotected debugfs reads
Source GCVE Database
Not known to be exploited · fixed in e1dea54496f90a62318cf4eeaa1e9ef8316e92b6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e1dea54496f90a62318cf4eeaa1e9ef8316e92b6, ce308ce18dedc18e9eeff8473892975e6fdd7aef, b7e507c6da8875da93b4130c8185e82a9dfd565c +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel by replacing debugfs_create_file_unsafe() with debugfs_create_file() for the affected debugfs file operations. Users should update to the fixed kernel version once available.
Description
A vulnerability in the Linux kernel's iio: imu: adis16480 driver involved unprotected debugfs reads. The firmware_revision and firmware_date file operations did not properly use debugfs_file_get(), causing debugfs_remove_recursive() to not wait for ongoing reads. This could lead to the iio_dev device being freed while still in use. The issue was fixed by replacing debugfs_create_file_unsafe() with debugfs_create_file().
References
- nvd.nist.gov/vuln/detail/CVE-2026-98663 (opens in a new tab)
- git.kernel.org/stable/c/396b83106f5e7d16467049f0caabd10533c01a0e (opens in a new tab)
- git.kernel.org/stable/c/b7e507c6da8875da93b4130c8185e82a9dfd565c (opens in a new tab)
- git.kernel.org/stable/c/ce308ce18dedc18e9eeff8473892975e6fdd7aef (opens in a new tab)
- git.kernel.org/stable/c/e1dea54496f90a62318cf4eeaa1e9ef8316e92b6 (opens in a new tab)