BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-54079High confidence

power: supply: bq27xxx: Fix poll_interval handling and races on remove

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

9 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-54079 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Linux kernel: Race condition in bq27xxx battery driver causes system instability
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the bq27xxx battery driver within the Linux kernel. This vulnerability involves a race condition and incorrect handling of the poll_interval during the driver's removal process. A local attacker with low privileges could exploit this flaw, causing the poll_interval to change unexpectedly and a delayed work item to be re-queued even after the device has been removed. This could lead to system instability or a denial of service.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-60366

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2025-2929Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0225Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-54060 Référence CVE CVE-2023-54064 https://www.cve.org/CVERecord?id=CVE-2023-54064 Référence CVE CVE-2023-54066 https://www.cve.org/CVERecord?id=CVE-2023-54066 Référence CVE CVE-2023-54067 https://www.cve.org/CVERecord?id=CVE-2023-54067 Référence CVE CVE-2023-54069 https://www.cve.org/CVERecord?id=CVE-2023-54069 Référence CVE CVE-2023-54070 https://www.cve.org/CVERecord?id=CVE-2023-54070 Référence CVE CVE-2023-54072 https://www.cve.org/CVERecord?id=CVE-2023-54072 Référence CVE CVE-2023-54076 https://www.cve.org/CVERecord?id=CVE-2023-54076 Référence CVE CVE-2023-54078 https://www.cve.org/CVERecord?id=CVE-2023-54078 Référence CVE CVE-2023-54079 https://www.cve.org/CVERecord?id=CVE-2023-54079 Référence CVE CVE-2023-54080 https://www.cve.org/CVERecord?id=CVE-2023-54080 Référence CVE CVE-2023-54081 https://www.cve.org/CVERecord?id=CVE-2023-54081 Référence CVE CVE-2023-54083 https://www.cve.org/CVERecord?id=CVE-2023-54083 Référence CVE CVE-2023-54084 https://www.cve.org/CVERecord?id=CVE-2023-54084 Référence CVE CVE-2023-54088 https://www.cve.org/CVERecord?id=CVE-2023-54088 Référence CVE CVE-2023-54089 https://www.cve.org/CVERecord?id=CVE-2023-54089 Référence CVE CVE-2023-54090 https://www.cve.org/CVERecord?id=CVE-2023-54090 Référence CVE CVE-2023-54091 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0170Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-54051 Référence CVE CVE-2023-54053 https://www.cve.org/CVERecord?id=CVE-2023-54053 Référence CVE CVE-2023-54055 https://www.cve.org/CVERecord?id=CVE-2023-54055 Référence CVE CVE-2023-54058 https://www.cve.org/CVERecord?id=CVE-2023-54058 Référence CVE CVE-2023-54064 https://www.cve.org/CVERecord?id=CVE-2023-54064 Référence CVE CVE-2023-54067 https://www.cve.org/CVERecord?id=CVE-2023-54067 Référence CVE CVE-2023-54072 https://www.cve.org/CVERecord?id=CVE-2023-54072 Référence CVE CVE-2023-54076 https://www.cve.org/CVERecord?id=CVE-2023-54076 Référence CVE CVE-2023-54078 https://www.cve.org/CVERecord?id=CVE-2023-54078 Référence CVE CVE-2023-54079 https://www.cve.org/CVERecord?id=CVE-2023-54079 Référence CVE CVE-2023-54083 https://www.cve.org/CVERecord?id=CVE-2023-54083 Référence CVE CVE-2023-54084 https://www.cve.org/CVERecord?id=CVE-2023-54084 Référence CVE CVE-2023-54090 https://www.cve.org/CVERecord?id=CVE-2023-54090 Référence CVE CVE-2023-54091 https://www.cve.org/CVERecord?id=CVE-2023-54091 Référence CVE CVE-2023-54092 https://www.cve.org/CVERecord?id=CVE-2023-54092 Référence CVE CVE-2023-54095 https://www.cve.org/CVERecord?id=CVE-2023-54095 Référence CVE CVE-2023-54096 https://www.cve.org/CVERecord?id=CVE-2023-54096 Référence CVE CVE-2023-54097 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0108Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-54064 Référence CVE CVE-2023-54066 https://www.cve.org/CVERecord?id=CVE-2023-54066 Référence CVE CVE-2023-54067 https://www.cve.org/CVERecord?id=CVE-2023-54067 Référence CVE CVE-2023-54069 https://www.cve.org/CVERecord?id=CVE-2023-54069 Référence CVE CVE-2023-54070 https://www.cve.org/CVERecord?id=CVE-2023-54070 Référence CVE CVE-2023-54072 https://www.cve.org/CVERecord?id=CVE-2023-54072 Référence CVE CVE-2023-54074 https://www.cve.org/CVERecord?id=CVE-2023-54074 Référence CVE CVE-2023-54076 https://www.cve.org/CVERecord?id=CVE-2023-54076 Référence CVE CVE-2023-54078 https://www.cve.org/CVERecord?id=CVE-2023-54078 Référence CVE CVE-2023-54079 https://www.cve.org/CVERecord?id=CVE-2023-54079 Référence CVE CVE-2023-54080 https://www.cve.org/CVERecord?id=CVE-2023-54080 Référence CVE CVE-2023-54081 https://www.cve.org/CVERecord?id=CVE-2023-54081 Référence CVE CVE-2023-54083 https://www.cve.org/CVERecord?id=CVE-2023-54083 Référence CVE CVE-2023-54084 https://www.cve.org/CVERecord?id=CVE-2023-54084 Référence CVE CVE-2023-54088 https://www.cve.org/CVERecord?id=CVE-2023-54088 Référence CVE CVE-2023-54089 https://www.cve.org/CVERecord?id=CVE-2023-54089 Référence CVE CVE-2023-54090 https://www.cve.org/CVERecord?id=CVE-2023-54090 Référence CVE CVE-2023-54091 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < 4c9615474fb0a41cfad658d78db3c9ec70912969; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < 465d919151a1e8d40daf366b868914f59d073211; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < 0c5f4cec759679c290720fbcf6bb81768e21c95b; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < e85757da9091998276ff21a13915ac25229cc232; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < e98e5bebfcafc75a7b41192a607dfea5c1268afa; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < d952a1eaafcc5f0351caad5dbe9b5b3300d1d529; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < b12faeca0e819ea09051a705fef9df7ea7e9e18c; 8cfaaa811894a3ae2d7360a15a6cfccff3ebc7db < c00bc80462afc7963f449d7f21d896d2f629cacc
Fixed
< 3.3; 4.14.316 ≤ 4.14.*; 4.19.284 ≤ 4.19.*; 5.4.244 ≤ 5.4.*; 5.10.181 ≤ 5.10.*; 5.15.114 ≤ 5.15.*; 6.1.31 ≤ 6.1.*; 6.3.5 ≤ 6.3.*
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Dec 2025 · Last source change 5 Aug 2026, 09:17 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-60366
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-60366↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-54079 · cve.blacktree.nl