From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98660: iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup
Date: Sun, 18 Oct 2026 17:43:55 +0200 [thread overview]
Message-ID: <2026101855-CVE-2026-98660-8f12@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup
The sampling frequency tables store each frequency as an integer part and
a fractional part in micro units. num_sampling_freq_avail is initialized
to the number of flattened integer elements because read_avail() returns
the table as a flat array.
bmp280_write_sampling_frequency(), however, indexes the same table as a
two-dimensional array and uses num_sampling_freq_avail as the number of
rows. Convert the flattened element count back to the number of rows
before iterating over the table.
The Linux kernel CVE team has assigned CVE-2026-98660 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 10b40ffba2f95cdeed47b731c5ad5ecc73e140e8 and fixed in 6.12.113 with commit 9db6684fab228edd3b8861a172ccbce3236f027a
Issue introduced in 6.1 with commit 10b40ffba2f95cdeed47b731c5ad5ecc73e140e8 and fixed in 6.18.56 with commit 4fd5a61e61d6899cbd45728a5fceba49a53c222d
Issue introduced in 6.1 with commit 10b40ffba2f95cdeed47b731c5ad5ecc73e140e8 and fixed in 7.2.10 with commit 7dbb518f3328ebd9d5c6e970b4befad6deb5c7f1
Issue introduced in 6.1 with commit 10b40ffba2f95cdeed47b731c5ad5ecc73e140e8 and fixed in 7.3-rc6 with commit 56c423b233b214182c58c99861899327b45b0d6c
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-98660
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/pressure/bmp280-core.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/9db6684fab228edd3b8861a172ccbce3236f027a
https://git.kernel.org/stable/c/4fd5a61e61d6899cbd45728a5fceba49a53c222d
https://git.kernel.org/stable/c/7dbb518f3328ebd9d5c6e970b4befad6deb5c7f1
https://git.kernel.org/stable/c/56c423b233b214182c58c99861899327b45b0d6c
reply other threads:[~2026-10-18 15:52 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=2026101855-CVE-2026-98660-8f12@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.