CVE-2026-45916

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1f472b14ad56104ba228b8fbec60d5b21829913
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca7dd71773e4e050b0fb98768b7eae60f8d1f38b
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d59cf3887fbabacef53bfba473e33e8a8d9d07b
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/861dda7a9074c0ff67788928165ae39d7f647491
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82d3eb97a976c9d56bb92b241397610e57a9c629
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8010b745b436c3e1ca5dd960aa29fa3e0f6d8841
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2078830c32d1e49ac942c6f8c21f35c806ae5e94
generic

power: supply: sbs-battery: Fix use-after-free in power_supply_changed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14d4dee5d8fb361bfff275832087254beab66d72

Vendor Advisories for CVE-2026-45916(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-25ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-25ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-25ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-25ubuntu
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (100 versions)6.18.14-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 81× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 214 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-25 05:44 UTCEG score recompute
  8. 2026-08-25 05:44 UTCVendor advisory
  9. 2026-08-25 05:43 UTCGHSA enrichment
  10. 2026-08-23 15:30 UTCEG score recompute
  11. 2026-08-23 15:30 UTCVendor advisory
  12. 2026-08-23 15:29 UTCGHSA enrichment
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 20:52 UTCVendor advisory
  16. 2026-08-21 20:52 UTCGHSA enrichment
  17. 2026-08-20 17:41 UTCEG score recompute
  18. 2026-08-20 17:41 UTCVendor advisory
  19. 2026-08-20 17:40 UTCGHSA enrichment
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 09:21 UTCVendor advisory
  24. 2026-08-17 09:21 UTCGHSA enrichment
  25. 2026-08-16 16:26 UTCEG score recompute
Show 75 more
  1. 2026-08-16 16:26 UTCVendor advisory
  2. 2026-08-16 16:26 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:54 UTCEG score recompute
  5. 2026-08-16 02:54 UTCVendor advisory
  6. 2026-08-16 02:54 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 02:30 UTCEG score recompute
  9. 2026-08-15 02:30 UTCVendor advisory
  10. 2026-08-15 02:30 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 14:02 UTCVendor advisory
  13. 2026-08-14 14:02 UTCGHSA enrichment
  14. 2026-08-14 01:34 UTCEG score recompute
  15. 2026-08-14 01:34 UTCVendor advisory
  16. 2026-08-14 01:34 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 04:14 UTCVendor advisory
  19. 2026-08-13 04:14 UTCGHSA enrichment
  20. 2026-08-12 15:47 UTCEG score recompute
  21. 2026-08-12 15:46 UTCVendor advisory
  22. 2026-08-12 15:46 UTCGHSA enrichment
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-12 03:00 UTCVendor advisory
  25. 2026-08-12 03:00 UTCGHSA enrichment
  26. 2026-08-11 14:19 UTCVendor advisory
  27. 2026-08-11 14:19 UTCGHSA enrichment
  28. 2026-08-11 01:41 UTCEG score recompute
  29. 2026-08-11 01:41 UTCVendor advisory
  30. 2026-08-11 01:41 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 13:13 UTCVendor advisory
  33. 2026-08-10 13:13 UTCGHSA enrichment
  34. 2026-08-10 00:45 UTCEG score recompute
  35. 2026-08-10 00:45 UTCVendor advisory
  36. 2026-08-10 00:45 UTCGHSA enrichment
  37. 2026-08-09 13:46 UTCEPSS rescore
  38. 2026-08-09 12:17 UTCVendor advisory
  39. 2026-08-09 12:17 UTCGHSA enrichment
  40. 2026-08-08 23:45 UTCEG score recompute
  41. 2026-08-08 23:45 UTCVendor advisory
  42. 2026-08-08 23:45 UTCGHSA enrichment
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-08 11:17 UTCVendor advisory
  45. 2026-08-08 11:17 UTCGHSA enrichment
  46. 2026-08-07 22:48 UTCEG score recompute
  47. 2026-08-07 22:48 UTCVendor advisory
  48. 2026-08-07 22:48 UTCGHSA enrichment
  49. 2026-08-07 10:20 UTCVendor advisory
  50. 2026-08-07 10:20 UTCGHSA enrichment
  51. 2026-08-06 21:52 UTCEG score recompute
  52. 2026-08-06 21:52 UTCVendor advisory
  53. 2026-08-06 21:52 UTCGHSA enrichment
  54. 2026-08-06 13:47 UTCEPSS rescore
  55. 2026-08-06 09:24 UTCVendor advisory
  56. 2026-08-06 09:24 UTCGHSA enrichment
  57. 2026-08-05 20:55 UTCEG score recompute
  58. 2026-08-05 20:55 UTCVendor advisory
  59. 2026-08-05 20:55 UTCGHSA enrichment
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-04 15:10 UTCEPSS rescore
  62. 2026-08-04 10:39 UTCEPSS rescore
  63. 2026-08-04 04:57 UTCVendor advisory
  64. 2026-08-04 04:57 UTCGHSA enrichment
  65. 2026-08-03 16:29 UTCVendor advisory
  66. 2026-08-03 16:29 UTCGHSA enrichment
  67. 2026-08-02 16:39 UTCVendor advisory
  68. 2026-08-02 16:39 UTCGHSA enrichment
  69. 2026-08-02 04:11 UTCEG score recompute
  70. 2026-08-02 04:11 UTCVendor advisory
  71. 2026-08-02 04:11 UTCGHSA enrichment
  72. 2026-08-02 02:27 UTCEPSS rescore
  73. 2026-08-01 15:42 UTCEG score recompute
  74. 2026-08-01 15:42 UTCVendor advisory
  75. 2026-08-01 15:42 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-45916?
CVE-2026-45916 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: power: supply: sbs-battery: Fix use-after-free in powersupplychanged() Using the devm variant for requesting IRQ before the devm variant for allocating/registering the power_supply handle, means that the powersupply handle will be…
When was CVE-2026-45916 disclosed?
CVE-2026-45916 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45916 actively exploited?
CVE-2026-45916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-45916?
CVE-2026-45916 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-45916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45916

Explore →

Is Your Infrastructure Affected by CVE-2026-45916?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.