From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43476: iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas()
Date: Wed, 13 May 2026 17:08:44 +0200 [thread overview]
Message-ID: <2026051344-CVE-2026-43476-0f4f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas()
sizeof(num) evaluates to sizeof(size_t) (8 bytes on 64-bit) instead
of the intended __be32 element size (4 bytes). Use sizeof(*meas) to
correctly match the buffer element type.
The Linux kernel CVE team has assigned CVE-2026-43476 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 5.15.203 with commit 9aff2e9c2927ecd9652872a43a0725f101128104
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.1.167 with commit 08881d82f94deaa51800360029908863e5c4c39d
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.6.130 with commit dcdf1e92674efb6692f4ebe189e0aa9fde23a541
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.12.78 with commit 2a4d111a6a34afb8bb4f118009e7728ed2ec7e10
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.18.19 with commit 90e978ace598567e6e30de79805bddf37cf892ac
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.19.9 with commit 165f12b40901c6a7aca15796da239726ddcdc5ad
Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 7.0 with commit 216345f98cae7fcc84f49728c67478ac00321c87
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-43476
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/chemical/sps30_i2c.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/9aff2e9c2927ecd9652872a43a0725f101128104
https://git.kernel.org/stable/c/08881d82f94deaa51800360029908863e5c4c39d
https://git.kernel.org/stable/c/dcdf1e92674efb6692f4ebe189e0aa9fde23a541
https://git.kernel.org/stable/c/2a4d111a6a34afb8bb4f118009e7728ed2ec7e10
https://git.kernel.org/stable/c/90e978ace598567e6e30de79805bddf37cf892ac
https://git.kernel.org/stable/c/165f12b40901c6a7aca15796da239726ddcdc5ad
https://git.kernel.org/stable/c/216345f98cae7fcc84f49728c67478ac00321c87
reply other threads:[~2026-05-13 15:08 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=2026051344-CVE-2026-43476-0f4f@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