High 7.8Published May 27, 2026

CVE-2026-45936power: supply: goldfish: Fix use-after-free in power_supply_changed()

Updated under an hour ago (Oct 26, 2026, 6:40 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: power: supply: goldfish: 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: 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Undergoing Analysis
Record last updated: May 27, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 84d7b768748943db2bb658b43931fdab04c224cc before 589d4fe56713c6344cd9f8939f9c7621c85f0966; from 84d7b768748943db2bb658b43931fdab04c224cc before bad8b61eb5059acd88349680e47839342dc89e94; from 84d7b768748943db2bb658b43931fdab04c224cc before 33751e28842bf5aee5ef7b2b8d5e456a069095cb; 84d7b768748943db2bb658b43931fdab04c224cc builds before 77ea437faa4c06362e3ecfd2d7264eaa7ac1e82c; from 84d7b768748943db2bb658b43931fdab04c224cc before 4350505e82b4f972ddb788e1c712c557c38859d0; 84d7b768748943db2bb658b43931fdab04c224cc builds before 8c89aade8335e26a6a7dcda18992d15f51943927; 84d7b768748943db2bb658b43931fdab04c224cc builds before 0b29ffe4090a3fc7a7649de20e1eb1e53adddac7; from 84d7b768748943db2bb658b43931fdab04c224cc before b2ce982e2e0c888dc55c888ad0e20ea04daf2e6b	CNA record
linux linux_kernel linux:linux_kernel	from 3.9 before 5.10.252; from 5.11 before 5.15.202; from 5.16 before 6.1.165; from 6.2 before 6.6.128; from 6.7 before 6.12.75; from 6.13 before 6.18.14; from 6.19 before 6.19.4	NVD

References

References

https://git.kernel.org/stable/c/589d4fe56713c6344cd9f8939f9c7621c85f0966	patch
https://git.kernel.org/stable/c/bad8b61eb5059acd88349680e47839342dc89e94	patch
https://git.kernel.org/stable/c/33751e28842bf5aee5ef7b2b8d5e456a069095cb	patch
https://git.kernel.org/stable/c/77ea437faa4c06362e3ecfd2d7264eaa7ac1e82c	patch
https://git.kernel.org/stable/c/4350505e82b4f972ddb788e1c712c557c38859d0	patch
https://git.kernel.org/stable/c/8c89aade8335e26a6a7dcda18992d15f51943927	patch
https://git.kernel.org/stable/c/0b29ffe4090a3fc7a7649de20e1eb1e53adddac7	patch
https://git.kernel.org/stable/c/b2ce982e2e0c888dc55c888ad0e20ea04daf2e6b	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.