power: supply: cpcap-battery: Fix use-after-free in power_supply_changed()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 874b2adbed1253a11549cb9b7b912ab65fea9cf2 · < 2841bbb5a35c4449c0a0458e8e476b2a62f95147| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
power: supply: cpcap-battery: Fix use-after-free in power_supply_changed()
Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run.
This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory...
Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`.
Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle.
From the CVE record · Linux
The Linux kernel’s cpcap-battery driver has a race that can use a freed power-supply handle if an interrupt fires during device removal. An interrupt during device probing can also use an uninitialized handle. These conditions can crash the system or corrupt memory; the input does not establish how an attacker could trigger them or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with the cpcap-battery driver should check their kernel versions; affected versions are not specified.