CVE-2026-98663 json
iio: imu: adis16480: fix unprotected debugfs reads
published 24d ago modified 12d ago also EUVD-2026-103917
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
iio: imu: adis16480: fix unprotected debugfs reads
The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.
Use debugfs_create_file() instead.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98663
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-43.43
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1017.18
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1017.19
- linux-gke Ubuntu 24.04 LTS 6.8.0-1068.77
- linux-gke Ubuntu 26.04 LTS 7.0.0-1010.11
ubuntu advisories UBUNTU-CVE-2026-98663
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1
- git.kernel.org/stable/c/8a7ff80c5cce57c65c105efd3a3e112edcce0e08 commit
- git.kernel.org/stable/c/cd2923032a9b8774e5a110c62c35919266387a2e commit
- git.kernel.org/stable/c/ef4a716c51e19c2f2565d9993c110e5ecc3b3783 commit
- git.kernel.org/stable/c/8a782244972715c76bdaf8b662e9b22e260c5296 commit
- git.kernel.org/stable/c/b7e507c6da8875da93b4130c8185e82a9dfd565c commit
- git.kernel.org/stable/c/ce308ce18dedc18e9eeff8473892975e6fdd7aef commit
- git.kernel.org/stable/c/396b83106f5e7d16467049f0caabd10533c01a0e commit
- git.kernel.org/stable/c/e1dea54496f90a62318cf4eeaa1e9ef8316e92b6 commit
Is CVE-2026-98663 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98663 updated cvss 4.1
kernel: iio: imu: adis16480: fix unprotected debugfs reads
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/8a7ff80c5cce57c65c105efd3a3e112edcce0e08
- git.kernel.org /stable/c/cd2923032a9b8774e5a110c62c35919266387a2e
- git.kernel.org /stable/c/ef4a716c51e19c2f2565d9993c110e5ecc3b3783
- git.kernel.org /stable/c/8a782244972715c76bdaf8b662e9b22e260c5296
- git.kernel.org /stable/c/b7e507c6da8875da93b4130c8185e82a9dfd565c
- git.kernel.org /stable/c/ce308ce18dedc18e9eeff8473892975e6fdd7aef
- git.kernel.org /stable/c/396b83106f5e7d16467049f0caabd10533c01a0e
- git.kernel.org /stable/c/e1dea54496f90a62318cf4eeaa1e9ef8316e92b6
Sources
- CVE List CVE-2026-98663
- NVD CVE-2026-98663
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.