From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98664: iio: imu: adis16400: fix unprotected debugfs reads
Date: Sun, 18 Oct 2026 17:43:59 +0200 [thread overview]
Message-ID: <2026101856-CVE-2026-98664-800c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-98664 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.8 with commit ae1d37a9bb4bd8d9091a40d153143e99b115ee37 and fixed in 6.12.113 with commit e9b4c00f775a915b759b08bfe2c5e806a8301a59
Issue introduced in 5.8 with commit ae1d37a9bb4bd8d9091a40d153143e99b115ee37 and fixed in 6.18.56 with commit 50e8d70ba0743f88afd7e49f9cebd1841ee677f5
Issue introduced in 5.8 with commit ae1d37a9bb4bd8d9091a40d153143e99b115ee37 and fixed in 7.2.10 with commit f501302ebb9e1504162351b951fe3ae331c852ab
Issue introduced in 5.8 with commit ae1d37a9bb4bd8d9091a40d153143e99b115ee37 and fixed in 7.3-rc6 with commit d94787287a113a1326211647d5e0deed1e9de105
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98664
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/iio/imu/adis16400.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e9b4c00f775a915b759b08bfe2c5e806a8301a59
https://git.kernel.org/stable/c/50e8d70ba0743f88afd7e49f9cebd1841ee677f5
https://git.kernel.org/stable/c/f501302ebb9e1504162351b951fe3ae331c852ab
https://git.kernel.org/stable/c/d94787287a113a1326211647d5e0deed1e9de105
reply other threads:[~2026-10-18 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026101856-CVE-2026-98664-800c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.