Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2023-54079power: supply: bq27xxx: Fix poll_interval handling and races on remove
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.37-1 | DEBIAN-CVE-2023-54079 |
| Debian:13 | linux | 6.3.7-1 | DEBIAN-CVE-2023-54079 |
| Debian:14 | linux | 6.3.7-1 | DEBIAN-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux | 5.15.0-83.92 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1044.49 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1046.53 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1046.53.1 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1041.49 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1041.46 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1027.32 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1037.40 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1039.45 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1041.46 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-83.92 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1032.32 | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1017.17 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1004.4 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1042.48 | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1037.40 | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54079 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-54079 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before 4c9615474fb0a41cfad658d78db3c9ec709129698cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before 465d919151a1e8d40daf366b868914f59d0732118cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before 0c5f4cec759679c290720fbcf6bb81768e21c95b8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before e85757da9091998276ff21a13915ac25229cc2328cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before e98e5bebfcafc75a7b41192a607dfea5c1268afa8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before d952a1eaafcc5f0351caad5dbe9b5b3300d1d5298cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before b12faeca0e819ea09051a705fef9df7ea7e9e18c8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db – before c00bc80462afc7963f449d7f21d896d2f629cacc |
| Linux | Linux | 3.3 |
References
- https://git.kernel.org/stable/c/4c9615474fb0a41cfad658d78db3c9ec70912969
- https://git.kernel.org/stable/c/465d919151a1e8d40daf366b868914f59d073211
- https://git.kernel.org/stable/c/0c5f4cec759679c290720fbcf6bb81768e21c95b
- https://git.kernel.org/stable/c/e85757da9091998276ff21a13915ac25229cc232
- https://git.kernel.org/stable/c/e98e5bebfcafc75a7b41192a607dfea5c1268afa
- https://git.kernel.org/stable/c/d952a1eaafcc5f0351caad5dbe9b5b3300d1d529
- https://git.kernel.org/stable/c/b12faeca0e819ea09051a705fef9df7ea7e9e18c
- https://git.kernel.org/stable/c/c00bc80462afc7963f449d7f21d896d2f629cacc