[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091553-CVE-2023-53166-12e5@gregkh>
Date: Mon, 15 Sep 2025 16:02:20 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53166: power: supply: bq25890: Fix external_power_changed race
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
power: supply: bq25890: Fix external_power_changed race
bq25890_charger_external_power_changed() dereferences bq->charger,
which gets sets in bq25890_power_supply_init() like this:
bq->charger = devm_power_supply_register(bq->dev, &bq->desc, &psy_cfg);
As soon as devm_power_supply_register() has called device_add()
the external_power_changed callback can get called. So there is a window
where bq25890_charger_external_power_changed() may get called while
bq->charger has not been set yet leading to a NULL pointer dereference.
This race hits during boot sometimes on a Lenovo Yoga Book 1 yb1-x90f
when the cht_wcove_pwrsrc (extcon) power_supply is done with detecting
the connected charger-type which happens to exactly hit the small window:
BUG: kernel NULL pointer dereference, address: 0000000000000018
<snip>
RIP: 0010:__power_supply_is_supplied_by+0xb/0xb0
<snip>
Call Trace:
<TASK>
__power_supply_get_supplier_property+0x19/0x50
class_for_each_device+0xb1/0xe0
power_supply_get_property_from_supplier+0x2e/0x50
bq25890_charger_external_power_changed+0x38/0x1b0 [bq25890_charger]
__power_supply_changed_work+0x30/0x40
class_for_each_device+0xb1/0xe0
power_supply_changed_work+0x5f/0xe0
<snip>
Fixing this is easy. The external_power_changed callback gets passed
the power_supply which will eventually get stored in bq->charger,
so bq25890_charger_external_power_changed() can simply directly use
the passed in psy argument which is always valid.
The Linux kernel CVE team has assigned CVE-2023-53166 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit eab25b4f93aa771728127705eb4b235a3b5aad94 and fixed in 6.1.31 with commit 72c28207c19c2c46fab8ae994aff25e197fb2949
Issue introduced in 5.18 with commit eab25b4f93aa771728127705eb4b235a3b5aad94 and fixed in 6.3.5 with commit 9d20fa1982c35697f3f8c4ae0f12791691ae5958
Issue introduced in 5.18 with commit eab25b4f93aa771728127705eb4b235a3b5aad94 and fixed in 6.4 with commit 029a443b9b6424170f00f6dd5b7682e682cce92e
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-2023-53166
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/bq25890_charger.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/72c28207c19c2c46fab8ae994aff25e197fb2949
https://git.kernel.org/stable/c/9d20fa1982c35697f3f8c4ae0f12791691ae5958
https://git.kernel.org/stable/c/029a443b9b6424170f00f6dd5b7682e682cce92e
Powered by blists - more mailing lists