power: supply: qcom_battmgr: terminate the strings from firmware
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's qcom_battmgr driver can leave firmware-provided strings unterminated. If firmware sends a string that fills a field, reading the affected power-supply property from user space can expose data from adjacent fields. The input does not specify an attacker access or authentication requirement.
Engineers running Linux kernels with the qcom_battmgr driver should check their kernel versions; affected versions were not specified.