Описание
In the Linux kernel, the following vulnerability has been resolved:
power: supply: charger-manager: fix refcount leak in is_full_charged()
In is_full_charged(), power_supply_get_by_name() is called to
obtain a reference to the fuel_gauge power supply. If the
voltage check (uV >= desc->fullbatt_uV) succeeds, the function
returns true directly without releasing the reference, leaking
the refcount.
Fix this by setting a flag and jumping to the out label where
power_supply_put() properly drops the reference.
A flaw was found in the Linux kernel's power supply charger-manager component. A reference count (refcount) leak occurs within the is_full_charged() function. This happens when a reference to the fuel gauge power supply is obtained but not properly released if a specific voltage check succeeds. This resource leak could potentially lead to system instability or a denial of service.
Отчет
A moderate-impact reference count (refcount) leak was found in the Linux kernel's power supply charger-manager driver (drivers/power/supply/charger-manager.c). In is_full_charged(), the reference to the fuel-gauge power supply obtained via power_supply_get_by_name() is not released with power_supply_put() when the full-battery voltage check (uV >= desc->fullbatt_uV) succeeds, so the reference leaks each time that check passes. A local attacker able to trigger repeated charger-manager battery-status evaluations could use this resource leak to exhaust kernel memory resources and cause a denial of service (system instability or crash). Red Hat rates this flaw Moderate severity with a CVSS:3.1 base score of 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), reflecting the local attack vector and the availability-only impact. The vulnerable code was introduced upstream in Linux kernel 5.10. All Red Hat Enterprise Linux 6, 7, 8, 9, and 10 streams (including the kernel and kernel-rt components) and all Red Hat In-Vehicle OS 2 streams (kernel and kernel-ivos-qualcomm components) are not affected because the vulnerable code is not present in the shipped kernels, so no Red Hat product update is required for this issue.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | ||
| Red Hat Enterprise Linux 6 | kernel | Not affected | ||
| Red Hat Enterprise Linux 7 | kernel | Not affected | ||
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | ||
| Red Hat Enterprise Linux 8 | kernel | Not affected | ||
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | ||
| Red Hat Enterprise Linux 9 | kernel | Not affected | ||
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Показывать по
Дополнительная информация
Статус:
5.5 Medium
CVSS3
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: power: supply: charger-manager: fix refcount leak in is_full_charged() In is_full_charged(), power_supply_get_by_name() is called to obtain a reference to the fuel_gauge power supply. If the voltage check (uV >= desc->fullbatt_uV) succeeds, the function returns true directly without releasing the reference, leaking the refcount. Fix this by setting a flag and jumping to the out label where power_supply_put() properly drops the reference.
In the Linux kernel, the following vulnerability has been resolved: power: supply: charger-manager: fix refcount leak in is_full_charged() In is_full_charged(), power_supply_get_by_name() is called to obtain a reference to the fuel_gauge power supply. If the voltage check (uV >= desc->fullbatt_uV) succeeds, the function returns true directly without releasing the reference, leaking the refcount. Fix this by setting a flag and jumping to the out label where power_supply_put() properly drops the reference.
In the Linux kernel, the following vulnerability has been resolved: p ...
5.5 Medium
CVSS3