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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
5.5%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 48× 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.

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

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 5.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.