Linux Kernel up to 6.3.4 poll_interval bq27xxx_battery_teardown privilege escalation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 6.3.4 and classified as critical. Affected is the function bq27xxx_battery_teardown of the file /sys/module/bq27xxx_battery/parameters/poll_interval. The manipulation leads to an unknown weakness.
This vulnerability is uniquely identified as CVE-2023-54079. No exploit exists.
The affected component should be upgraded.
Details
A vulnerability was found in Linux Kernel up to 6.3.4 and classified as critical. This issue affects the function bq27xxx_battery_teardown of the file /sys/module/bq27xxx_battery/parameters/poll_interval. The impact remains unknown. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-54079 since 12/24/2025. The exploitation is known to be difficult. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/02/2026).
The vulnerability scanner Nessus provides a plugin with the ID 280050 (Linux Distros Unpatched Vulnerability : CVE-2023-54079), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.114, 6.1.31 or 6.3.5 eliminates this vulnerability. Applying the patch 4c9615474fb0a41cfad658d78db3c9ec70912969/465d919151a1e8d40daf366b868914f59d073211/0c5f4cec759679c290720fbcf6bb81768e21c95b/e85757da9091998276ff21a13915ac25229cc232/e98e5bebfcafc75a7b41192a607dfea5c1268afa/d952a1eaafcc5f0351caad5dbe9b5b3300d1d529/b12faeca0e819ea09051a705fef9df7ea7e9e18c/c00bc80462afc7963f449d7f21d896d2f629cacc is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (280050) and CERT Bund (WID-SEC-2025-2929). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 4.14.315
- 4.19.283
- 5.4.243
- 5.10.180
- 5.15.113
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 6.1.29
- 6.1.30
- 6.3.0
- 6.3.1
- 6.3.2
- 6.3.3
- 6.3.4
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 280050
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-54079
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.14.316/4.19.284/5.4.244/5.10.181/5.15.114/6.1.31/6.3.5
Patch: 4c9615474fb0a41cfad658d78db3c9ec70912969/465d919151a1e8d40daf366b868914f59d073211/0c5f4cec759679c290720fbcf6bb81768e21c95b/e85757da9091998276ff21a13915ac25229cc232/e98e5bebfcafc75a7b41192a607dfea5c1268afa/d952a1eaafcc5f0351caad5dbe9b5b3300d1d529/b12faeca0e819ea09051a705fef9df7ea7e9e18c/c00bc80462afc7963f449d7f21d896d2f629cacc
Timeline
12/24/2025 Advisory disclosed12/24/2025 CVE reserved
12/24/2025 VulDB entry created
01/02/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-54079 (🔒)
GCVE (CVE): GCVE-0-2023-54079
GCVE (VulDB): GCVE-100-338117
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 12/24/2025 15:12Updated: 01/02/2026 21:55
Changes: 12/24/2025 15:12 (58), 12/27/2025 03:59 (2), 01/02/2026 21:55 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.