Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-45867: power: supply: act8945a: Fix use-after-free in power_supply_changed()

Noroxi assessment

Priority: Monitor (action score 31/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.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0768e8525a46df103647ca5059b32320d7fd17e4, 3291c51d4684d048dd2eb91b5b65fcfdaf72141f, 697bb5dc0cb4791e244f3970b067bc1ef33be9d9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0768e8525a46df103647ca5059b32320d7fd17e4, 3291c51d4684d048dd2eb91b5b65fcfdaf72141f, 697bb5dc0cb4791e244f3970b067bc1ef33be9d9 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: act8945a: 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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Jun 25, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2026-45867

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel4.9 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

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.9affected
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before f2a0777b1e5a3cee1712c4d3e9095c0df8fc8cb3affected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before 0768e8525a46df103647ca5059b32320d7fd17e4affected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before d023ef9f748b2090f7a9dbdd5c622b6ad99088eaaffected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before 697bb5dc0cb4791e244f3970b067bc1ef33be9d9affected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before 76a42ba547a9b2e2337894f67a4d9247445007d5affected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before f27eb76def5c07e4d7cc468b40741f19dafc83ceaffected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before 83c1bd466c514cb24ca6ef347c5aac76a13c4e1eaffected · git
    • a09209acd6a808794bdd7866af3678d1fd1d90e7 and later · before 3291c51d4684d048dd2eb91b5b65fcfdaf72141faffected · git
    • before 4.9not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.18.14-16.18.14-1

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-45865May 27, 2026 · mctp i2c: initialise event handler read bytes
    22Monitor
  • ← EarlierCVE-2026-45866May 27, 2026 · serial: caif: fix use-after-free in caif_serial ldisc_close()
    31Monitor
  • Later →CVE-2026-45868May 27, 2026 · pinctrl: single: fix refcount leak in pcs_add_gpio_func()
    22Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Linux Linux0768e8525a46df103647ca5059b32320d7fd17e4Vendor (CNA)
Linux Linux3291c51d4684d048dd2eb91b5b65fcfdaf72141fVendor (CNA)
Linux Linux697bb5dc0cb4791e244f3970b067bc1ef33be9d9Vendor (CNA)
Linux Linux76a42ba547a9b2e2337894f67a4d9247445007d5Vendor (CNA)
Linux Linux83c1bd466c514cb24ca6ef347c5aac76a13c4e1eVendor (CNA)
Linux Linuxd023ef9f748b2090f7a9dbdd5c622b6ad99088eaVendor (CNA)
Linux Linuxf27eb76def5c07e4d7cc468b40741f19dafc83ceVendor (CNA)
Linux Linuxf2a0777b1e5a3cee1712c4d3e9095c0df8fc8cb3Vendor (CNA)
debian:linux6.1.170-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • 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
Low
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:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

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.

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

Vulnerable

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

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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✗ → ✓

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

References

All records