CVE-2026-45902

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: 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.

Overview

State: PUBLISHED
Assigner (CNA): Linux
CVSS severity: high
CVSS score: 7.1 / 10
CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Effective score: 7.1 / 10 HIGH source: CNA overview
CWE(s): —
Reserved: 2026-05-13
Published: 2026-05-27 12:17 UTC
Last updated: 2026-05-27 12:17 UTC
Source: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/45xxx/CVE-2026-45902.json
Linked Threat: CVE-2026-45902 — CVE-2026-45902

NVD triage scoring NVD CVE 2.0

Layer NVD adds on top of the CNA's CVE record — published / last-modified timestamps, exploitability / impact subscores, and the FIRST.org EPSS probability that this CVE will be exploited in the wild in the next 30 days.

NVD published: 2026-05-27 14:17:04 UTC
NVD last modified: 2026-06-24 16:29:02 UTC
NVD CVSS v3.1: 7.8 / 10 HIGH source: nvd@nist.gov
NVD CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Exploitability subscore: 1.8 / 10
Impact subscore: 5.9 / 10
EPSS score: 0.0016 (probability of exploitation in next 30 days)
EPSS percentile: 5.54% vs all CVEs — higher = more likely to be exploited, as of 2026-07-26

NVD-assigned CWE(s): CWE-416 (differs from the CNA list above)

European Union Vulnerability Database ENISA EUVD

ENISA's official EU repository for curated vulnerability intelligence. Carries a separate identifier (EUVD-YYYY-NNNN) and frequently exposes an earlier-published description + CVSS than NVD does.

EUVD ID: EUVD-2026-32368
Assigner: Linux
Published: May 27, 2026, 12:17:10 PM
Updated: May 27, 2026, 12:17:10 PM
EUVD base score: 0.0 / 10
EUVD-reported EPSS: 0.1600
Vendors: Linux
Products: Linux (patch: 6.12.75)

Linux (patch: 6.18.14)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <cb5c743936edcebc51880eeb6bf04979b5c9438b)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <83c27fdd696ac13d023ef7a0345301be93209c53)

Linux (patch: 6.19.4)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <8005843369723d9c8975b7c4202d1b85d6125302)

Linux (5.12)

Linux (patch: 6.6.128)

Linux (patch: 0)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <81d3688c9a2158329391e08f2d0b8ba204216044)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <8796910131a32ff29275052df768ef022929a394)

Linux (patch: 6.1.165)

Linux (patch: 7.0)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <4b6fb0b6124f558131e502e3ffd03e6583b3ace6)

Linux (32e4978bb920d047fe5de3ea42d176f267c01f63 <74b5a88318db97d51bb40f774736553c2acd1514)

Linux (patch: 5.15.202)
Aliases: GHSA-h63c-9r2v-9cmw

ENISA description: In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: 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.

EUVD references (7)

Affected products (2)

Vendor	Product	Versions	Platforms
Linux	Linux	`32e4978bb920d047fe5de3ea42d176f267c01f63` (affected), `32e4978bb920d047fe5de3ea42d176f267c01f63` (affected), `32e4978bb920d047fe5de3ea42d176f267c01f63` (affected), `32e4978bb920d047fe5de3ea42d176f267c01f63` (affected), `32e4978bb920d047fe5de3ea42d176f267c01f63` (affected), `32e4978bb920d047fe5de3ea42d176f267c01f63` (affected), `32e4978bb920d047fe5de3ea42d176f267c01f63` (affected)	—
Linux	Linux	`5.12` (affected), `0` (unaffected), `5.15.202` (unaffected), `6.1.165` (unaffected), `6.6.128` (unaffected), `6.12.75` (unaffected), `6.18.14` (unaffected), `6.19.4` (unaffected), `7.0` (unaffected)	—

Affected products — CPE 2.3 (1) NVD

NVD's normalized CPE 2.3 matchers, used by vendor tools (vulnerability scanners, asset managers) for automated detection. Compare with the CNA's free-text "Affected products" section above.

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

Vendor references (7)

References embedded in the original CVE record by the assigning CNA.

Web references (10)

DuckDuckGo results ranked by threat-intel / vendor advisory domains. Generated by the 🔎 Find references (web) button above — same flow as the Remediations search.

https://git.kernel.org/stable/c/4b6fb0b6124f558131e502e3ffd03e6583b3ace6 tenable:git.kernel.org
https://git.kernel.org/stable/c/74b5a88318db97d51bb40f774736553c2acd1514 tenable:git.kernel.org
https://git.kernel.org/stable/c/8005843369723d9c8975b7c4202d1b85d6125302 tenable:git.kernel.org
https://git.kernel.org/stable/c/81d3688c9a2158329391e08f2d0b8ba204216044 tenable:git.kernel.org
https://git.kernel.org/stable/c/83c27fdd696ac13d023ef7a0345301be93209c53 tenable:git.kernel.org
https://git.kernel.org/stable/c/8796910131a32ff29275052df768ef022929a394 tenable:git.kernel.org
https://git.kernel.org/stable/c/cb5c743936edcebc51880eeb6bf04979b5c9438b tenable:git.kernel.org
https://nvd.nist.gov/vuln/detail/CVE-2026-45902 tenable:nvd.nist.gov
https://www.cve.org/CVERecord?id=CVE-2026-45902 tenable:www.cve.org
https://www.first.org/epss/ tenable:www.first.org

NVD-tagged references (7)

Reference list NVD curates from the CNA record, vendor advisories, and third-party reports. The tag chips below are NVD's analyst-assigned categories.

https://git.kernel.org/stable/c/4b6fb0b6124f558131e502e3ffd03e6583b3ace6 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/74b5a88318db97d51bb40f774736553c2acd1514 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/8005843369723d9c8975b7c4202d1b85d6125302 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/81d3688c9a2158329391e08f2d0b8ba204216044 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/83c27fdd696ac13d023ef7a0345301be93209c53 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/8796910131a32ff29275052df768ef022929a394 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/cb5c743936edcebc51880eeb6bf04979b5c9438b 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch

Remediations (17)

Remediations are stored against the linked Threat row; the list below is deduplicated across both pages.

Microsoft and Adobe Patch Tuesday, May 2026 Security Update Review

web:blog.qualys.com

May 2026's Patch Tuesday arrives with Microsoft addressing a fresh set of vulnerabilities across its ecosystem, reinforcing the ongoing need for timely patching in an increasingly threat-heavy…

2026-06-04 00:16 UTC
Microsoft Patch Tuesday May 2026 - 120 Vulnerabilities Fixed, Including ...

web:cybersecuritynews.com

Microsoft's May 2026 Patch Tuesday lands with a heavy enterprise focus, fixing 120 vulnerabilities across Windows, Office, Azure, developer tools, and Microsoft 365 apps, including 29 remote code execution (RCE) flaws rated Critical.

2026-06-04 00:16 UTC
Security Update Guide - Microsoft

web:portal.msrc.microsoft.com

The Security Update Guide provides information on the latest Microsoft security updates, helping users understand and address potential vulnerabilities effectively.

2026-06-04 00:16 UTC
SharePoint Has a New RCE Flaw. If You Haven't Patched Yet, Go Do That.

web:securityaffairs.com

A critical vulnerability ( CVE - 2026 -45659) in Microsoft SharePoint can allow attackers to achieve remote code execution with little effort.

2026-06-04 00:16 UTC
Landing Page | ServiceNow Common Vulnerabilities & Exposures (CVE ...

web:support.servicenow.com

Overview The advisories below document publicly disclosed Common Vulnerabilities and Exposures ( CVEs ) in the Now Platform by ServiceNow. Because ServiceNow uses various methods to communicate vulnerability information, patches, and other fixes, customers should review family, security patch , and hotfix release notes, which are available at https://docs.servicenow.com, for a complete list of ...

2026-06-04 00:16 UTC
Microsoft March 2026 Patch Tuesday fixes 2 zero-days, 79 flaws

web:www.bleepingcomputer.com

Today is Microsoft's March 2026 Patch Tuesday with security updates for 79 flaws, including 2 publicly disclosed zero-day vulnerabilities.

2026-06-04 00:16 UTC
Microsoft Patch Tuesday - May 2026 - Lansweeper

web:www.lansweeper.com

Which vulnerabilities, issues, and other things did Microsoft update? Discover what's new using Lansweeper's Patch Tuesday May 2026 summary.

2026-06-04 00:16 UTC
Microsoft Defender vulnerabilities are being exploited in the wild

web:www.malwarebytes.com

The KEV catalog tracks vulnerabilities known to be exploited in the wild and sets patch deadlines for Federal Civilian Executive Branch (FCEB) agencies. Five of the added vulnerabilities are quite old by vulnerability standards. Patches were released in 2008, 2009, and 2010. But the Microsoft Defender vulnerabilities are from this year. Those ...

2026-06-04 00:16 UTC
Oracle Critical Patch Update Advisory - April 2026

web:www.oracle.com

This Critical Patch Update contains 481 new security patches across the product families listed below. Please note that an MOS note summarizing the content of this Critical Patch Update and other Oracle Software Security Assurance activities is located at April 2026 Critical Patch Update: Executive Summary and Analysis.

2026-06-04 00:16 UTC
Patch Tuesday June 2026: Security Updates & CVE Analysis

web:zecurit.com

Get the complete breakdown of Microsoft's June 2026 Patch Tuesday. We analyze the latest security updates and all critical CVEs .

2026-06-04 00:16 UTC
Microsoft Confirms Defender RoguePlanet 0-Day Exploit and Working to ...

web:cybersecuritynews.com

Microsoft has officially acknowledged a critical zero-day vulnerability in Microsoft Defender, publicly dubbed "RoguePlanet," and confirmed it is actively developing a security patch to address the flaw.

2026-06-19 02:27 UTC
Security Update Guide - Microsoft Security Response Center

web:msrc.microsoft.com

Security Update Guide - Microsoft Security Response Center

2026-06-19 02:27 UTC
Nvd - Cve-2026-10902

web:nvd.nist.gov

An official website of the United States government Here's how you know

2026-06-19 02:27 UTC
2 New Microsoft Defender Zero-Days Exploited—Patch Now Rolling Out

web:tech.yahoo.com

Microsoft has now confirmed two new Microsoft Defender zero-days that it said had been exploited. This exploitation was confirmed by CISA, which has added the security flaws to its Known Exploited Vulnerabilities catalog and given federal agencies until June 3 to ensure mitigation measures are in place.

2026-06-19 02:27 UTC
May 2026 Patch Tuesday: Updates and Analysis | CrowdStrike

web:www.crowdstrike.com

Microsoft has released security updates for 130 vulnerabilities, including 30 critical, in its May 2026 Patch Tuesday rollout.

2026-06-19 02:27 UTC
Microsoft patches two zero-day flaws in Defender - CSO Online

web:www.csoonline.com

Microsoft released emergency fixes for two zero-day vulnerabilities in the malware protection components of Microsoft Defender. The flaws allow local attackers to gain system-level privileges or ...

2026-06-19 02:27 UTC
Microsoft working on a fix for RoguePlanet, a flaw that grants full PC ...

web:www.malwarebytes.com

Microsoft says it's working on a fix for an unpatched Defender vulnerability that can give attackers the highest level of access on Windows.

2026-06-19 02:27 UTC

AI Forensic Analysis

Only Available for Registered Users. Sign in to view.

Raw JSON

The full cvelistV5 record. Download as CVE-2026-45902.json.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/power/supply/bq256xx_charger.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "81d3688c9a2158329391e08f2d0b8ba204216044",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            },
            {
              "lessThan": "74b5a88318db97d51bb40f774736553c2acd1514",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            },
            {
              "lessThan": "cb5c743936edcebc51880eeb6bf04979b5c9438b",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            },
            {
              "lessThan": "83c27fdd696ac13d023ef7a0345301be93209c53",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            },
            {
              "lessThan": "4b6fb0b6124f558131e502e3ffd03e6583b3ace6",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            },
            {
              "lessThan": "8796910131a32ff29275052df768ef022929a394",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            },
            {
              "lessThan": "8005843369723d9c8975b7c4202d1b85d6125302",
              "status": "affected",
              "version": "32e4978bb920d047fe5de3ea42d176f267c01f63",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/power/supply/bq256xx_charger.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.12"
            },
            {
              "lessThan": "5.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.202",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.165",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.128",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.75",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.14",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.202",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.165",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.128",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.75",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.14",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.4",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: bq256xx: Fix use-after-free in power_supply_changed()\n\nUsing the `devm_` variant for requesting IRQ _before_ the `devm_`\nvariant for allocating/registering the `power_supply` handle, means that\nthe `power_supply` handle will be deallocated/unregistered _before_ the\ninterrupt handler (since `devm_` naturally deallocates in reverse\nallocation order). This means that during removal, there is a race\ncondition where an interrupt can fire just _after_ the `power_supply`\nhandle has been freed, *but* just _before_ the corresponding\nunregistration of the IRQ handler has run.\n\nThis will lead to the IRQ handler calling `power_supply_changed()` with\na freed `power_supply` handle. Which usually crashes the system or\notherwise silently corrupts the memory...\n\nNote that there is a similar situation which can also happen during\n`probe()`; the possibility of an interrupt firing _before_ registering\nthe `power_supply` handle. This would then lead to the nasty situation\nof using the `power_supply` handle *uninitialized* in\n`power_supply_changed()`.\n\nFix this racy use-after-free by making sure the IRQ is requested _after_\nthe registration of the `power_supply` handle."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-27T12:17:10.508Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/81d3688c9a2158329391e08f2d0b8ba204216044"
        },
        {
          "url": "https://git.kernel.org/stable/c/74b5a88318db97d51bb40f774736553c2acd1514"
        },
        {
          "url": "https://git.kernel.org/stable/c/cb5c743936edcebc51880eeb6bf04979b5c9438b"
        },
        {
          "url": "https://git.kernel.org/stable/c/83c27fdd696ac13d023ef7a0345301be93209c53"
        },
        {
          "url": "https://git.kernel.org/stable/c/4b6fb0b6124f558131e502e3ffd03e6583b3ace6"
        },
        {
          "url": "https://git.kernel.org/stable/c/8796910131a32ff29275052df768ef022929a394"
        },
        {
          "url": "https://git.kernel.org/stable/c/8005843369723d9c8975b7c4202d1b85d6125302"
        }
      ],
      "title": "power: supply: bq256xx: Fix use-after-free in power_supply_changed()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-45902",
    "datePublished": "2026-05-27T12:17:10.508Z",
    "dateReserved": "2026-05-13T15:03:33.084Z",
    "dateUpdated": "2026-05-27T12:17:10.508Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}