From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43307: iio: accel: adxl380: Avoid reading more entries than present in FIFO
Date: Fri, 8 May 2026 15:12:12 +0200 [thread overview]
Message-ID: <2026050858-CVE-2026-43307-5b3e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: accel: adxl380: Avoid reading more entries than present in FIFO
The interrupt handler reads FIFO entries in batches of N samples, where N
is the number of scan elements that have been enabled. However, the sensor
fills the FIFO one sample at a time, even when more than one channel is
enabled. Therefore,the number of entries reported by the FIFO status
registers may not be a multiple of N; if this number is not a multiple, the
number of entries read from the FIFO may exceed the number of entries
actually present.
To fix the above issue, round down the number of FIFO entries read from the
status registers so that it is always a multiple of N.
The Linux kernel CVE team has assigned CVE-2026-43307 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit df36de13677a0ebd3ab31dd2c603f9eafdf8de7d and fixed in 6.12.75 with commit a40f316085985f916ba1599fc303fdbc6a078e86
Issue introduced in 6.12 with commit df36de13677a0ebd3ab31dd2c603f9eafdf8de7d and fixed in 6.18.16 with commit a8e88edfd69df7b63c882aa53e61e7c078806ad7
Issue introduced in 6.12 with commit df36de13677a0ebd3ab31dd2c603f9eafdf8de7d and fixed in 6.19.6 with commit f42ddb2945ae4ce2b6f1c2e7aae9f14455a734d3
Issue introduced in 6.12 with commit df36de13677a0ebd3ab31dd2c603f9eafdf8de7d and fixed in 7.0 with commit c1b14015224cfcccd5356333763f2f4f401bd810
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-43307
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/accel/adxl380.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/a40f316085985f916ba1599fc303fdbc6a078e86
https://git.kernel.org/stable/c/a8e88edfd69df7b63c882aa53e61e7c078806ad7
https://git.kernel.org/stable/c/f42ddb2945ae4ce2b6f1c2e7aae9f14455a734d3
https://git.kernel.org/stable/c/c1b14015224cfcccd5356333763f2f4f401bd810
reply other threads:[~2026-05-08 13:14 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=2026050858-CVE-2026-43307-5b3e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox