NVD / CVE Program· CNA Linux

CVE-2026-46270: power: supply: rt9455: Fix use-after-free in power_supply_changed()

HighCVSS 8.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 33/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 2178dc65d45e2f7bcaa8af8d80d100419bdab251, 62d753b916bd500bb269b7078cdab73198ab4718, 64e15155095f39f4dec9b4659da1238ef8fc54d4.

Low priority for now. Upgrade to Linux Linux 2178dc65d45e2f7bcaa8af8d80d100419bdab251, 62d753b916bd500bb269b7078cdab73198ab4718, 64e15155095f39f4dec9b4659da1238ef8fc54d4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Memory safety

BDU:2026-11809

Published: Jun 3, 2026
Updated: Aug 5, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 33 / 40 · 8.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · Linux: 8.4; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.2affected
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before d4e2e3c3caa26b93aa9f36d0a6824b584e2a8dfcaffected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before 62d753b916bd500bb269b7078cdab73198ab4718affected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before a39f8f06216f73ef40e71e2fe4ad071964c1fd36affected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before af261f218a7606f93d2c786353d60bb4feb56ef0affected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before 2178dc65d45e2f7bcaa8af8d80d100419bdab251affected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before 64e15155095f39f4dec9b4659da1238ef8fc54d4affected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before 721449a15170fc5f028a7576d7f65b9f60d53482affected · git
- e86d69dd786e94046b8f5be7df1b9a8226a40b2a and later · before e2febe375e5ea5afed92f4cd9711bde8f24ee6d2affected · git
- before 4.2not affected · semver

Affected versions · NVD (7)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel4.2 and later · before 5.10.252
linux linux kernel5.11 and later · before 5.15.202
linux linux kernel5.16 and later · before 6.1.165
linux linux kernel6.2 and later · before 6.6.128
linux linux kernel6.7 and later · before 6.12.75
linux linux kernel6.13 and later · before 6.18.14
linux linux kernel6.19 and later · before 6.19.4

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.170-1	6.1.170-1
Debian:13	linux	before 6.12.85-1	6.12.85-1
Debian:14	linux	before 6.18.14-1	6.18.14-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-46268Jun 3, 2026 · PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition
22Monitor
← EarlierCVE-2026-46269Jun 3, 2026 · pinctrl: canaan: k230: Fix NULL pointer dereference when parsing devicetree
22Monitor
Later →CVE-2026-46273Jun 3, 2026 · ibmveth: Disable GSO for packets with small MSS
34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	2178dc65d45e2f7bcaa8af8d80d100419bdab251	Vendor (CNA)
Linux Linux	62d753b916bd500bb269b7078cdab73198ab4718	Vendor (CNA)
Linux Linux	64e15155095f39f4dec9b4659da1238ef8fc54d4	Vendor (CNA)
Linux Linux	721449a15170fc5f028a7576d7f65b9f60d53482	Vendor (CNA)
Linux Linux	a39f8f06216f73ef40e71e2fe4ad071964c1fd36	Vendor (CNA)
Linux Linux	af261f218a7606f93d2c786353d60bb4feb56ef0	Vendor (CNA)
Linux Linux	d4e2e3c3caa26b93aa9f36d0a6824b584e2a8dfc	Vendor (CNA)
Linux Linux	e2febe375e5ea5afed92f4cd9711bde8f24ee6d2	Vendor (CNA)
debian:linux	6.1.170-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records