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-45916power: supply: sbs-battery: Fix use-after-free in power_supply_changed()

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: sbs-battery: 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()`. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle. Keep the old behavior of just printing a warning in case of any failures during the IRQ request and finishing the probe successfully.

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-45916, by who scored it
Scored byCVSSScoreVector
NVDNVD · Undergoing Analysis3.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 94% of all CVEs (16 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 d2cec82c28802da31596b395ad292cb8f132fd63 – < ca7dd71773e4e050b0fb98768b7eae60f8d1f38b
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < f1f472b14ad56104ba228b8fbec60d5b21829913
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < 8010b745b436c3e1ca5dd960aa29fa3e0f6d8841
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < 2078830c32d1e49ac942c6f8c21f35c806ae5e94
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < 82d3eb97a976c9d56bb92b241397610e57a9c629
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < 861dda7a9074c0ff67788928165ae39d7f647491
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < 14d4dee5d8fb361bfff275832087254beab66d72
    • affected d2cec82c28802da31596b395ad292cb8f132fd63 – < 8d59cf3887fbabacef53bfba473e33e8a8d9d07b
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.252 – ≤ 5.10.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .