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-89464power: supply: twl4030_charger: cancel workers via devm

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: twl4030_charger: cancel workers via devm bci is devm-allocated. Two workers (bci->work and bci->current_worker) dereference it. twl4030_bci_remove() disables charging and masks interrupts. It cancels neither worker. A worker pending at remove() can run after devm frees bci. The USB transceiver comes from devm_usb_get_phy_by_node(). devm unregisters its notifier only after remove() returns. A cancel_work_sync() in remove() can then race a notifier reschedule. devm_work_autocancel() and devm_delayed_work_autocancel() avoid that. They cancel the workers during devm release, before bci is freed. The current_worker is registered first, since devm will cancel in reverse order and bci->work can reschedule current_worker. [Move comment about order into the commit message]

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 (13 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 d6ccc442b12102414c1343f0adacaa8a1aaa516c – < 9644c96ef8646c65d46caa5139a6631e29b79d6c
    • affected d6ccc442b12102414c1343f0adacaa8a1aaa516c – < e9fffe10bd791082263c1678f2f6cdd6d7b487e0
    • affected d6ccc442b12102414c1343f0adacaa8a1aaa516c – < c46c205bab0dfce4dd54aeb49da3f183e1fdfc63
    • affected d6ccc442b12102414c1343f0adacaa8a1aaa516c – < 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458
    • affected d6ccc442b12102414c1343f0adacaa8a1aaa516c – < a4460e89d4088cfec2da5be33e265ef1a8e780e9
    • affected d6ccc442b12102414c1343f0adacaa8a1aaa516c – < b955da82db4170bdf1c784dc457287aa0c977378
    • affected d6ccc442b12102414c1343f0adacaa8a1aaa516c – < 6eba34732524067da2aad5ddfdfbc641ded10e9e
  • Linux · Linux

    • affected 2.6.39
    • unaffected < 2.6.39
    • 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-89464 badge
[![CVE-2026-89464](https://cveledger.app/badge/CVE-2026-89464.svg)](https://cveledger.app/cve/CVE-2026-89464)

Record last updated .