NVD / CVE Program· CNA Linux

CVE-2026-45879: power: supply: bq25980: 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 03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7c, 0560a4b09c92e2ecaa883965cf6f9ca51c158ff9, 0de95d29d847c6217b7d5845e24a71a4aee7b359.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7c, 0560a4b09c92e2ecaa883965cf6f9ca51c158ff9, 0de95d29d847c6217b7d5845e24a71a4aee7b359 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: bq25980: 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

Memory safety

BDU:2026-11764

Published: May 27, 2026
Updated: Jun 25, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-416

Report tools

JSON

Action score

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.

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.

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

Affected versions

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

linux linux kernel5.10 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
- 5.10affected
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 86f93dfb23f5bf4f285c4256a7e909d222f7de56affected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 16875e3b7bc9e59bfa0acaf1e43f275a6f42a30faffected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 0560a4b09c92e2ecaa883965cf6f9ca51c158ff9affected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 0de95d29d847c6217b7d5845e24a71a4aee7b359affected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 4aeaf03c17260415c2fdd55992f9ad4188d5455aaffected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7caffected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before abea607ff2f62f4c0a5fb29f7fbdaaab163276a4affected · git
- 5069185fc18e810715a91d80fcd075e03add600c and later · before 5f0b1cb41906e86b64bf69f5ededb83b0d757c27affected · git
- before 5.10not affected · semver

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-45875May 27, 2026 · mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure
22Monitor
← EarlierCVE-2026-45876May 27, 2026 · arm64/gcs: Fix error handling in arch_set_shadow_stack_status()
22Monitor
Later →CVE-2026-45880May 27, 2026 · PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails
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 / package	Fixed version	Source
Linux Linux	03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7c	Vendor (CNA)
Linux Linux	0560a4b09c92e2ecaa883965cf6f9ca51c158ff9	Vendor (CNA)
Linux Linux	0de95d29d847c6217b7d5845e24a71a4aee7b359	Vendor (CNA)
Linux Linux	16875e3b7bc9e59bfa0acaf1e43f275a6f42a30f	Vendor (CNA)
Linux Linux	4aeaf03c17260415c2fdd55992f9ad4188d5455a	Vendor (CNA)
Linux Linux	5f0b1cb41906e86b64bf69f5ededb83b0d757c27	Vendor (CNA)
Linux Linux	86f93dfb23f5bf4f285c4256a7e909d222f7de56	Vendor (CNA)
Linux Linux	abea607ff2f62f4c0a5fb29f7fbdaaab163276a4	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.

No history yet (it accumulates with the daily EPSS job).

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.

Credits

All researchers

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.

TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)

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.

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

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

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

References

git.kernel.org/stable/c/03d1e4ee4e6aa6d2966e883e4ca0e5be73bf1b7c

Show all references (7 more)

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

All records