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-45946power: supply: ab8500: Fix use-after-free in power_supply_changed()

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500: Fix use-after-free in power_supply_changed() Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory... Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`. Commit 1c1f13a006ed ("power: supply: ab8500: Move to componentized binding") introduced this issue during a refactorization. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

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

CVSS scores of CVE-2026-45946, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < 43cbb78ee047b9b12d096d40e3be265969d4c1f8
    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < 551672981fe227122258a25a385a05f5c0746ad6
    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < f50433f2603def08b21a4bf2fd238687fb5cbde9
    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < 847eeb6c0efcd76c7def73857cf798a4fcd8f79b
    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < 709db4b476e254579d9c48ec34d397a41ca0c407
    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < 46dbda27b028d78087667e8280966b99cec015ca
    • affected 1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb – < c4af8a98bb52825a5331ae1d0604c0ea6956ba4b
    • affected 341db343768bc44f3512facc464021730d64071c
    • affected 5.13.4 – < 5.14
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.14 – ≤ 6.18.*
    • unaffected 6.19.4 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .