CVE-2026-45902

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: bq256xx: 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
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (7)

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

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

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

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

https://git.kernel.org/stable/c/8796910131a32ff29275052df768ef022929a394
generic

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

https://git.kernel.org/stable/c/83c27fdd696ac13d023ef7a0345301be93209c53
generic

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

https://git.kernel.org/stable/c/81d3688c9a2158329391e08f2d0b8ba204216044
generic

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

https://git.kernel.org/stable/c/8005843369723d9c8975b7c4202d1b85d6125302
generic

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

https://git.kernel.org/stable/c/74b5a88318db97d51bb40f774736553c2acd1514
generic

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

https://git.kernel.org/stable/c/4b6fb0b6124f558131e502e3ffd03e6583b3ace6

Vendor Advisories for CVE-2026-45902(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-raspi-6.8 (6.8.0-1060.64) @ 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-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-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-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-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-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ 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-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-25ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-25ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-25ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-25ubuntu
linuxKernel @ 5.15.202osv

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

(3 across 3 ecosystems)
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 4× in last 7d / 85× 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 223 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45902?
CVE-2026-45902 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: 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-45902 disclosed?
CVE-2026-45902 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-45902 actively exploited?
CVE-2026-45902 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-45902?
CVE-2026-45902 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-45902?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45902, 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-45902

Explore →

Is Your Infrastructure Affected by CVE-2026-45902?

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