Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89474

power: supply: bq256xx: drain usb_work before freeing the charger

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: drain usb_work before freeing the charger The USB-PHY notifier queues usb_work, whose handler calls power_supply_changed(bq->charger). The reset devm action only unregisters the notifier and was registered before the power supplies, so devm frees bq->charger on unwind before the action runs; a usb_work still queued can then dereference it. Register the reset action after the power supplies, so it unregisters the notifiers and drains usb_work before the supplies are released. Initialize usb_work and obtain the PHY references before registering the notifiers, so the worker cannot run before the supplies exist. Found by static analysis.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < 9dcfdf6c598301b278f0b3490eb2bf4f600524e2
    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < fd08d4dbbec07a44f01b0ddb041912be0dc88f8c
    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < 2cfb59dc9df8b5ebdd95e3d874a7f4690cee2bc8
    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < 9a467bd1e6811011026ad4c8de701b940d88a00c
    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < 9e1aba34df9a87d53460888e05718717c0f69343
    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < c8addb842ae8dcf69c15fc976e33e3bd538a41d7
    • affected 32e4978bb920d047fe5de3ea42d176f267c01f63 – < 2dd6cd823777bea6d9a880a12a92a73ec76aee0b
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89474 badge
[![CVE-2026-89474](https://cveledger.app/badge/CVE-2026-89474.svg)](https://cveledger.app/cve/CVE-2026-89474)

Record last updated .