Skip to content
Systems

CVE-2026-46270

8.4
High
EPSS 0.13%Patch availableJun 5, 2026

Linux kernel power_supply IRQ use-after-free race; may crash system

common questions

Is CVE-2026-46270 being exploited?

Not confirmed. CVE-2026-46270 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-46270?

CVE-2026-46270 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46270?

Yes. A fix has been recorded for CVE-2026-46270. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46270 affect?

CVE-2026-46270 affects Linux kernel (power_supply subsystem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46270?

Apply kernel patch with rt9455 fix

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (power_supply subsystem)
impact

IRQ may fire after power_supply handle is freed, causing crash or memory corruption

action required

Patch when possible

affected versions
Linux Linux
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < d4e2e3c3caa26b93aa9f36d0a6824b584e2a8dfc
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < 62d753b916bd500bb269b7078cdab73198ab4718
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < a39f8f06216f73ef40e71e2fe4ad071964c1fd36
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < af261f218a7606f93d2c786353d60bb4feb56ef0
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < 2178dc65d45e2f7bcaa8af8d80d100419bdab251
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < 64e15155095f39f4dec9b4659da1238ef8fc54d4
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < 721449a15170fc5f028a7576d7f65b9f60d53482
  • affected>= e86d69dd786e94046b8f5be7df1b9a8226a40b2a and < e2febe375e5ea5afed92f4cd9711bde8f24ee6d2
  • affected4.2
vendor says fixed in< 4.2, >= 5.10.252 and <= 5.10.*, >= 5.15.202 and <= 5.15.*, >= 6.1.165 and <= 6.1.*, >= 6.6.128 and <= 6.6.*, >= 6.12.75 and <= 6.12.*, >= 6.18.14 and <= 6.18.*, >= 6.19.4 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free