Linux vulnerability

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.

Published 11 Sep 2026Updated 13 Sep 20264 sources
CVSS 7.7

What happened

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.

Affected versions

Linux: 29e8142b5623b5949587bcc4f591c4e6595c4aca through before 0e70a9b0d16acf7adebc4f386178a95da27c0027 (git); 29e8142b5623b5949587bcc4f591c4e6595c4aca through before ee053561e21ce1e1741dd64ca5ddcdb92e40edc1 (git); 29e8142b5623b5949587bcc4f591c4e6595c4aca through before 6cc6c28c9ab6e8ecf901397717a5b391b828cdaf (git); 29e8142b5623b5949587bcc4f591c4e6595c4aca through before ab1112df8f4ffa88cb024dd370c432ced80f77d8 (git); 6.3 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.