CVE-2026-45938

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

power: supply: pm8916_lbc: 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)
EPSS
2.6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (4)

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

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

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

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

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

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

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

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

https://git.kernel.org/stable/c/08e674e9862a2db46fb234eb7c5442455ece0131

Vendor Advisories for CVE-2026-45938(1)

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

Patch Availability(8)

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.

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 7× in last 7d / 50× 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-19 02:29 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-13 22:30 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 01:56 UTCVendor advisory
  12. 2026-07-12 01:56 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 00:21 UTCGHSA enrichment
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-01 11:35 UTCGHSA enrichment
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 03:59 UTCGHSA enrichment
  24. 2026-06-29 14:28 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 67 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-28 21:20 UTCGHSA enrichment
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 07:26 UTCGHSA enrichment
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-27 18:44 UTCGHSA enrichment
  8. 2026-06-27 06:13 UTCGHSA enrichment
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 17:12 UTCGHSA enrichment
  11. 2026-06-26 02:44 UTCGHSA enrichment
  12. 2026-06-25 14:09 UTCGHSA enrichment
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 01:39 UTCEG score recompute 7.80
  15. 2026-06-25 01:39 UTCGHSA enrichment
  16. 2026-06-24 18:02 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
  26. 2026-06-19 19:26 UTCEPSS rescore
  27. 2026-06-19 19:26 UTCEPSS rescore
  28. 2026-06-18 17:52 UTCEPSS rescore
  29. 2026-06-18 17:52 UTCEPSS rescore
  30. 2026-06-16 17:52 UTCEPSS rescore
  31. 2026-06-15 22:52 UTCGHSA enrichment
  32. 2026-06-15 17:49 UTCEPSS rescore
  33. 2026-06-13 23:00 UTCEPSS rescore
  34. 2026-06-12 23:25 UTCGHSA enrichment
  35. 2026-06-12 23:12 UTCEPSS rescore
  36. 2026-06-12 23:12 UTCEPSS rescore
  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 23:59 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-07 00:33 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-04 01:07 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:40 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:16 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45938?
CVE-2026-45938 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: power: supply: pm8916lbc: Fix use-after-free in powersupply_changed() 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-45938 disclosed?
CVE-2026-45938 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-45938 actively exploited?
CVE-2026-45938 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45938?
CVE-2026-45938 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-45938?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45938, 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-45938

Explore →

Is Your Infrastructure Affected by CVE-2026-45938?

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