CVE-2026-46270

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: NoneExposed: 0

A fix is available — apply it.

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

power: supply: rt9455: 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
8.4
EG Score
8.4(medium)
EPSS
2.9%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 9, 2026

Advisory Details (8)

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

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

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

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

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

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

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

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

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

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

https://git.kernel.org/stable/c/721449a15170fc5f028a7576d7f65b9f60d53482
generic

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

https://git.kernel.org/stable/c/64e15155095f39f4dec9b4659da1238ef8fc54d4
generic

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

https://git.kernel.org/stable/c/62d753b916bd500bb269b7078cdab73198ab4718
generic

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

https://git.kernel.org/stable/c/2178dc65d45e2f7bcaa8af8d80d100419bdab251

Vendor Advisories for CVE-2026-46270(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 18× in last 7d / 108× 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 166 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46270?
CVE-2026-46270 is a high vulnerability published on June 3, 2026. In the Linux kernel, the following vulnerability has been resolved: power: supply: rt9455: 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-46270 disclosed?
CVE-2026-46270 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46270 actively exploited?
CVE-2026-46270 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46270?
CVE-2026-46270 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-46270?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46270, 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-46270

Explore →

Is Your Infrastructure Affected by CVE-2026-46270?

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