CVE-2026-45879

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: bq25980: 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 25, 2026

Advisory Details (8)

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

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

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

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

https://git.kernel.org/stable/c/86f93dfb23f5bf4f285c4256a7e909d222f7de56
generic

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

https://git.kernel.org/stable/c/5f0b1cb41906e86b64bf69f5ededb83b0d757c27
generic

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

https://git.kernel.org/stable/c/4aeaf03c17260415c2fdd55992f9ad4188d5455a
generic

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

https://git.kernel.org/stable/c/16875e3b7bc9e59bfa0acaf1e43f275a6f42a30f
generic

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

https://git.kernel.org/stable/c/0de95d29d847c6217b7d5845e24a71a4aee7b359
generic

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

https://git.kernel.org/stable/c/0560a4b09c92e2ecaa883965cf6f9ca51c158ff9
generic

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

https://git.kernel.org/stable/c/03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7c

Vendor Advisories for CVE-2026-45879(1)

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

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-25ubuntu
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-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-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-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
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ 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-fips-5.15 (5.15.0.1117.102) @ 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

(23)

Data Freshness Timeline

(refreshed 3× 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 217 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-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 05:48 UTCEG score recompute
  9. 2026-08-25 05:48 UTCVendor advisory
  10. 2026-08-25 05:48 UTCGHSA enrichment
  11. 2026-08-23 15:37 UTCEG score recompute
  12. 2026-08-23 15:37 UTCVendor advisory
  13. 2026-08-23 15:37 UTCGHSA enrichment
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 20:58 UTCEG score recompute
  17. 2026-08-21 20:58 UTCVendor advisory
  18. 2026-08-21 20:57 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 17:43 UTCEG score recompute
  21. 2026-08-20 17:43 UTCVendor advisory
  22. 2026-08-20 17:43 UTCGHSA enrichment
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 13:48 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-14 23:41 UTCVendor advisory
  13. 2026-08-14 23:41 UTCGHSA enrichment
  14. 2026-08-14 12:38 UTCVendor advisory
  15. 2026-08-14 12:38 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 09:52 UTCVendor advisory
  21. 2026-08-13 09:51 UTCGHSA enrichment
  22. 2026-08-12 22:46 UTCEG score recompute
  23. 2026-08-12 22:46 UTCVendor advisory
  24. 2026-08-12 22:46 UTCGHSA enrichment
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-12 11:43 UTCVendor advisory
  27. 2026-08-12 11:43 UTCGHSA enrichment
  28. 2026-08-12 00:39 UTCVendor advisory
  29. 2026-08-12 00:39 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 07:10 UTCVendor advisory
  37. 2026-08-10 07:10 UTCGHSA enrichment
  38. 2026-08-09 20:07 UTCEG score recompute
  39. 2026-08-09 20:07 UTCVendor advisory
  40. 2026-08-09 20:07 UTCGHSA enrichment
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-09 09:04 UTCVendor advisory
  43. 2026-08-09 09:04 UTCGHSA enrichment
  44. 2026-08-08 22:01 UTCEG score recompute
  45. 2026-08-08 22:01 UTCVendor advisory
  46. 2026-08-08 22:01 UTCGHSA enrichment
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-08 04:14 UTCVendor advisory
  49. 2026-08-08 04:14 UTCGHSA enrichment
  50. 2026-08-07 17:11 UTCEG score recompute
  51. 2026-08-07 17:11 UTCVendor advisory
  52. 2026-08-07 17:11 UTCGHSA enrichment
  53. 2026-08-07 06:08 UTCVendor advisory
  54. 2026-08-07 06:08 UTCGHSA enrichment
  55. 2026-08-06 19:03 UTCEG score recompute
  56. 2026-08-06 19:03 UTCVendor advisory
  57. 2026-08-06 19:03 UTCGHSA enrichment
  58. 2026-08-06 13:47 UTCEPSS rescore
  59. 2026-08-06 08:00 UTCVendor advisory
  60. 2026-08-06 08:00 UTCGHSA enrichment
  61. 2026-08-05 20:56 UTCEG score recompute
  62. 2026-08-05 20:56 UTCVendor advisory
  63. 2026-08-05 20:56 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:37 UTCVendor advisory
  68. 2026-08-04 03:37 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:56 UTCVendor advisory
  74. 2026-08-03 00:56 UTCGHSA enrichment
  75. 2026-08-02 13:53 UTCVendor advisory

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-45879?

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