From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72479: iio: accel: mma8452: handle I2C read error(s) in mma8452_read()
Date: Sat, 15 Aug 2026 15:09:18 +0900 [thread overview]
Message-ID: <2026081536-CVE-2026-72479-5e38@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: accel: mma8452: handle I2C read error(s) in mma8452_read()
Currently, If i2c_smbus_read_i2c_block_data() fails but
mma8452_set_runtime_pm_state() succeeds, mma8452_read() returns 0.
As a result, the caller mma8452_read_raw() assumes the read was
successful and proceeds to use a buffer containing uninitialized
stack memory.
Add proper checking of the I2C read return value and propagate errors
to the caller.
The Linux kernel CVE team has assigned CVE-2026-72479 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 5.10.261 with commit b488055e81d9faaaf2f8aaff45f9944040ac4493
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 5.15.212 with commit f9ec3f3e9cf27dd06cd3725eeaa44e3ce46be893
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 6.1.178 with commit b4932fc325e84a3233413daf230b043818c8a824
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 6.6.145 with commit eed69f8a10b82989ad732ace0fb43a9fb4e7fe35
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 6.12.97 with commit f3d905ea1e4996d933074481e80d96ecd74a9904
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 6.18.40 with commit 1cddef80a180af74c33d2f26c962ce92b60fded4
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 7.1.5 with commit f3d413e701c5e54bef736b638967724dda880365
Issue introduced in 4.7 with commit 96c0cb2bbfe0a58bd0c37cf34d50a20f9cd75aa8 and fixed in 7.2-rc1 with commit 5bdff291d20c31b365d9ddfe9c426fbfb41da5bb
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-72479
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/mma8452.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/b488055e81d9faaaf2f8aaff45f9944040ac4493
https://git.kernel.org/stable/c/f9ec3f3e9cf27dd06cd3725eeaa44e3ce46be893
https://git.kernel.org/stable/c/b4932fc325e84a3233413daf230b043818c8a824
https://git.kernel.org/stable/c/eed69f8a10b82989ad732ace0fb43a9fb4e7fe35
https://git.kernel.org/stable/c/f3d905ea1e4996d933074481e80d96ecd74a9904
https://git.kernel.org/stable/c/1cddef80a180af74c33d2f26c962ce92b60fded4
https://git.kernel.org/stable/c/f3d413e701c5e54bef736b638967724dda880365
https://git.kernel.org/stable/c/5bdff291d20c31b365d9ddfe9c426fbfb41da5bb
reply other threads:[~2026-08-15 6:30 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=2026081536-CVE-2026-72479-5e38@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.