CVE-2026-46270

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. the CNA's CVSS baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 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)
EG Risk
42(Track)
EG Risk 42/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
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 3, 2026

Last Modified

August 5, 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(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1057.58~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
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 (103 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 10× in last 7d / 46× 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 288 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 05:31 UTCEG score recompute
  3. 2026-09-14 05:31 UTCVendor advisory
  4. 2026-09-14 05:30 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 23:36 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 03:38 UTCEG score recompute
  23. 2026-08-25 03:38 UTCVendor advisory
  24. 2026-08-25 03:38 UTCGHSA enrichment
  25. 2026-08-24 00:08 UTCVendor advisory
Show 75 more
  1. 2026-08-24 00:07 UTCGHSA enrichment
  2. 2026-08-23 12:47 UTCEG score recompute
  3. 2026-08-23 12:47 UTCVendor advisory
  4. 2026-08-23 12:46 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 20:13 UTCVendor advisory
  8. 2026-08-21 20:13 UTCGHSA enrichment
  9. 2026-08-21 08:37 UTCVendor advisory
  10. 2026-08-21 08:36 UTCGHSA enrichment
  11. 2026-08-20 21:20 UTCVendor advisory
  12. 2026-08-20 21:20 UTCGHSA enrichment
  13. 2026-08-20 10:01 UTCEG score recompute
  14. 2026-08-20 10:01 UTCVendor advisory
  15. 2026-08-20 10:00 UTCGHSA enrichment
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 14:58 UTCEG score recompute
  19. 2026-08-17 14:58 UTCVendor advisory
  20. 2026-08-17 14:57 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 03:44 UTCEG score recompute
  23. 2026-08-17 03:44 UTCVendor advisory
  24. 2026-08-17 03:44 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 14:56 UTCVendor advisory
  27. 2026-08-16 14:56 UTCGHSA enrichment
  28. 2026-08-16 02:17 UTCEG score recompute
  29. 2026-08-16 02:17 UTCVendor advisory
  30. 2026-08-16 02:17 UTCGHSA enrichment
  31. 2026-08-16 02:14 UTCEPSS rescore
  32. 2026-08-15 14:43 UTCEG score recompute
  33. 2026-08-15 14:43 UTCVendor advisory
  34. 2026-08-15 14:43 UTCGHSA enrichment
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 21:23 UTCVendor advisory
  37. 2026-08-14 21:23 UTCGHSA enrichment
  38. 2026-08-14 10:09 UTCVendor advisory
  39. 2026-08-14 10:09 UTCGHSA enrichment
  40. 2026-08-13 22:55 UTCEG score recompute
  41. 2026-08-13 22:55 UTCVendor advisory
  42. 2026-08-13 22:55 UTCGHSA enrichment
  43. 2026-08-13 22:00 UTCEPSS rescore
  44. 2026-08-13 07:58 UTCVendor advisory
  45. 2026-08-13 07:58 UTCGHSA enrichment
  46. 2026-08-12 19:49 UTCEG score recompute
  47. 2026-08-12 19:49 UTCVendor advisory
  48. 2026-08-12 19:49 UTCGHSA enrichment
  49. 2026-08-12 13:51 UTCEPSS rescore
  50. 2026-08-12 08:35 UTCVendor advisory
  51. 2026-08-12 08:35 UTCGHSA enrichment
  52. 2026-08-11 21:06 UTCEG score recompute
  53. 2026-08-11 21:06 UTCVendor advisory
  54. 2026-08-11 21:06 UTCGHSA enrichment
  55. 2026-08-11 09:51 UTCEG score recompute
  56. 2026-08-11 09:51 UTCVendor advisory
  57. 2026-08-11 09:51 UTCGHSA enrichment
  58. 2026-08-11 00:00 UTCEPSS rescore
  59. 2026-08-10 22:37 UTCVendor advisory
  60. 2026-08-10 22:37 UTCGHSA enrichment
  61. 2026-08-10 06:24 UTCVendor advisory
  62. 2026-08-10 06:24 UTCGHSA enrichment
  63. 2026-08-09 19:11 UTCEG score recompute
  64. 2026-08-09 19:11 UTCVendor advisory
  65. 2026-08-09 19:11 UTCGHSA enrichment
  66. 2026-08-09 13:46 UTCEPSS rescore
  67. 2026-08-09 07:57 UTCVendor advisory
  68. 2026-08-09 07:57 UTCGHSA enrichment
  69. 2026-08-08 20:43 UTCEG score recompute
  70. 2026-08-08 20:43 UTCVendor advisory
  71. 2026-08-08 20:43 UTCGHSA enrichment
  72. 2026-08-08 16:37 UTCEPSS rescore
  73. 2026-08-08 09:28 UTCVendor advisory
  74. 2026-08-08 09:28 UTCGHSA enrichment
  75. 2026-08-07 22:14 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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46270?
CVE-2026-46270 has a CVSS v4.0 base score of 8.4 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.