CVE-2026-45882

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: pm8916_bms_vm: 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.

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
5%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (4)

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

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

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

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

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

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

https://git.kernel.org/stable/c/62914959b35e9a1e29cc0f64cb8cfc5075a5366f
generic

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

https://git.kernel.org/stable/c/17db6b3abd823c9fba3f3413c4f0f432d99d49dc

Vendor Advisories for CVE-2026-45882(1)

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

Patch Availability(13)

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

(2 across 2 ecosystems)
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

(12)

Data Freshness Timeline

(refreshed 5× in last 7d / 84× 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 213 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45882?
CVE-2026-45882 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: power: supply: pm8916bmsvm: 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-45882 disclosed?
CVE-2026-45882 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45882 actively exploited?
CVE-2026-45882 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-45882?
CVE-2026-45882 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-45882?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45882, 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-45882

Explore →

Is Your Infrastructure Affected by CVE-2026-45882?

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