CVE-2023-54079 In the Linux kernel, the following vulnerability has been resolved: power: supply: bq27xxx: Fix poll_interval handling…
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Linux 6.4 | earliest → < 6.4 | 6.4 |
| Linux 6.3 | earliest → < 6.3.5 | 6.3.5 |
| Linux 6.1 | earliest → < 6.1.31 | 6.1.31 |
| Linux 5.15 | earliest → < 5.15.114 | 5.15.114 |
| Linux 5.10 | earliest → < 5.10.181 | 5.10.181 |
| Linux 5.4 | earliest → < 5.4.244 | 5.4.244 |
| Linux 4.19 | earliest → < 4.19.284 | 4.19.284 |
| Linux 4.14 | earliest → < 4.14.316 | 4.14.316 |
| Linux | 3.3 | No fix stated |
Description
In the Linux kernel, the following vulnerability has been resolved: power: supply: bq27xxx: Fix poll_interval handling and races on remove Before this patch bq27xxx_battery_teardown() was setting poll_interval = 0 to avoid bq27xxx_battery_update() requeuing the delayed_work item. There are 2 problems with this: 1. If the driver is unbound through sysfs, rather then the module being rmmod-ed, this changes poll_interval unexpectedly 2. This is racy, after it being set poll_interval could be changed before bq27xxx_battery_update() checks it through /sys/module/bq27xxx_battery/parameters/poll_interval Fix this by added a removed attribute to struct bq27xxx_device_info and using that instead of setting poll_interval to 0. There also is another poll_interval related race on remove(), writing /sys/module/bq27xxx_battery/parameters/poll_interval will requeue the delayed_work item for all devices on the bq27xxx_battery_devices list and the device being removed was only removed from that list after cancelling the delayed_work item. Fix this by moving the removal from the bq27xxx_battery_devices list to before cancelling the delayed_work item.