CVE-2026-98666: Linux kernel · iio: gyro: adis16136: fix unprotected debugfs reads
Source GCVE Database
Not known to be exploited · fixed in d5b0b62e26d7d30e0e16e2d695f2161f7e92a5a5 : 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 d5b0b62e26d7d30e0e16e2d695f2161f7e92a5a5, b62c3944c006cff85dad881ba2948b2f3ef5a626, b53dc6e15aead039bc6a5e08060c96786240c81d +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 that replaces debugfs_create_file_unsafe() with debugfs_create_file() in the affected driver code. Users should apply the official Linux kernel patches that address this issue. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation.
Description
A vulnerability in the Linux kernel's iio gyro driver (adis16136) related to unprotected debugfs reads has been resolved. The issue stems from the serial_number file operations not calling debugfs_file_get(), which is required by debugfs_create_file_unsafe(). This causes debugfs_remove_recursive() to not wait for ongoing reads, potentially leading to use-after-free conditions when the device is unbound. The fix involves replacing debugfs_create_file_unsafe() with debugfs_create_file().
References
- nvd.nist.gov/vuln/detail/CVE-2026-98666 (opens in a new tab)
- git.kernel.org/stable/c/2b498df75d6c29aa3e760127ae0f0003df598b53 (opens in a new tab)
- git.kernel.org/stable/c/b05e768420352d9051f86c1a1f20f44fa046ba45 (opens in a new tab)
- git.kernel.org/stable/c/b53dc6e15aead039bc6a5e08060c96786240c81d (opens in a new tab)
- git.kernel.org/stable/c/d5b0b62e26d7d30e0e16e2d695f2161f7e92a5a5 (opens in a new tab)