From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89466: power: supply: qcom_battmgr: terminate the strings from firmware
Date: Fri, 11 Sep 2026 21:42:35 +0200 [thread overview]
Message-ID: <2026091102-CVE-2026-89466-8491@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
power: supply: qcom_battmgr: terminate the strings from firmware
The qcom_battmgr_sc8280xp_strcpy() takes a Pascal-style string when the
firmware sends one. Otherwise it copies all BATTMGR_STRING_LEN bytes and
leaves the destination without a terminator.
Those destinations are model_number, serial_number and oem_info, each
BATTMGR_STRING_LEN and declared next to each other. They go out to user
space as val->strval, which power_supply_format_property() prints with
"%s", so a firmware string that fills the whole field makes that read run
into the following members.
Use strscpy() so the copy always terminates, the way the SM8350 path
already does for the same field.
The Linux kernel CVE team has assigned CVE-2026-89466 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 6.12.109 with commit 0e70a9b0d16acf7adebc4f386178a95da27c0027
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 6.18.50 with commit ee053561e21ce1e1741dd64ca5ddcdb92e40edc1
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 7.2.4 with commit 6cc6c28c9ab6e8ecf901397717a5b391b828cdaf
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 7.3-rc1 with commit ab1112df8f4ffa88cb024dd370c432ced80f77d8
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-89466
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/qcom_battmgr.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/0e70a9b0d16acf7adebc4f386178a95da27c0027
https://git.kernel.org/stable/c/ee053561e21ce1e1741dd64ca5ddcdb92e40edc1
https://git.kernel.org/stable/c/6cc6c28c9ab6e8ecf901397717a5b391b828cdaf
https://git.kernel.org/stable/c/ab1112df8f4ffa88cb024dd370c432ced80f77d8
reply other threads:[~2026-09-11 19:51 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=2026091102-CVE-2026-89466-8491@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.