power: supply: qcom_battmgr: terminate the strings from firmware
Summary
| CVE | CVE-2026-89466 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-11 20:19:27 UTC |
| Updated | 2026-09-11 20:19:27 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 29e8142b5623b5949587bcc4f591c4e6595c4aca 0e70a9b0d16acf7adebc4f386178a95da27c0027 git |
Not specified |
| CNA |
Linux |
Linux |
affected 29e8142b5623b5949587bcc4f591c4e6595c4aca ee053561e21ce1e1741dd64ca5ddcdb92e40edc1 git |
Not specified |
| CNA |
Linux |
Linux |
affected 29e8142b5623b5949587bcc4f591c4e6595c4aca 6cc6c28c9ab6e8ecf901397717a5b391b828cdaf git |
Not specified |
| CNA |
Linux |
Linux |
affected 29e8142b5623b5949587bcc4f591c4e6595c4aca ab1112df8f4ffa88cb024dd370c432ced80f77d8 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.3 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.3 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.109 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.50 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.4 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/6cc6c28c9ab6e8ecf901397717a5b391b828cdaf |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ee053561e21ce1e1741dd64ca5ddcdb92e40edc1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ab1112df8f4ffa88cb024dd370c432ced80f77d8 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0e70a9b0d16acf7adebc4f386178a95da27c0027 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.