iio: imu: adis16480: fix unprotected debugfs reads
CVE-2026-98663 is fixed in 12 products on 1 platform, first by DEBIAN-CVE-2026-98663, released October 19, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.90.1.150700.17.51.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-livepatch-SLE15-SP7_Update_24 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.113-1 | DEBIAN-CVE-2026-98663 | Oct 19, 2026 |
| linux · Debian 14 | 7.2.10-1 | DEBIAN-CVE-2026-98663 | Oct 19, 2026 |
| linux-6.12 · Debian 12.15 (bookworm) | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-98663 | Oct 19, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.