From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74271: power: supply: core: fix supplied_from allocations
Date: Sat, 15 Aug 2026 15:09:58 +0900 [thread overview]
Message-ID: <2026081544-CVE-2026-74271-3497@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
power: supply: core: fix supplied_from allocations
If dts property power-supplies has multiple values, then accessing to
psy->supplied_from[i-1] in __power_supply_populate_supplied_from will
overrun supplied_from array.
The Linux kernel CVE team has assigned CVE-2026-74271 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.10 with commit f6e0b081fb300a4601b064346963cf6bb163f437 and fixed in 6.1.178 with commit ae55e4bf18ee0c4c170797dd65e17dbdf644fcf2
Issue introduced in 3.10 with commit f6e0b081fb300a4601b064346963cf6bb163f437 and fixed in 6.6.145 with commit 23a29ee1d9de38b7d6226b27653bc736b28ff05a
Issue introduced in 3.10 with commit f6e0b081fb300a4601b064346963cf6bb163f437 and fixed in 6.12.97 with commit fefc9dad30d545be288d50a0b10d00465015fcfe
Issue introduced in 3.10 with commit f6e0b081fb300a4601b064346963cf6bb163f437 and fixed in 6.18.40 with commit d0503357653ee62188987a26baa2d7f3689f367e
Issue introduced in 3.10 with commit f6e0b081fb300a4601b064346963cf6bb163f437 and fixed in 7.1.5 with commit 14357ba006e1586e4b4e809c074b21baf0aa4c4b
Issue introduced in 3.10 with commit f6e0b081fb300a4601b064346963cf6bb163f437 and fixed in 7.2-rc1 with commit ba61aed9a34671222d1149acfc2f0179a9ce7e80
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-74271
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/power/supply/power_supply_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/ae55e4bf18ee0c4c170797dd65e17dbdf644fcf2
https://git.kernel.org/stable/c/23a29ee1d9de38b7d6226b27653bc736b28ff05a
https://git.kernel.org/stable/c/fefc9dad30d545be288d50a0b10d00465015fcfe
https://git.kernel.org/stable/c/d0503357653ee62188987a26baa2d7f3689f367e
https://git.kernel.org/stable/c/14357ba006e1586e4b4e809c074b21baf0aa4c4b
https://git.kernel.org/stable/c/ba61aed9a34671222d1149acfc2f0179a9ce7e80
reply other threads:[~2026-08-15 6:32 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=2026081544-CVE-2026-74271-3497@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.