CVE-2026-45885

CVEs › CVE-2026-45885

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-battery: 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: 8.4 / 10
CVSS vector: AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Effective score: 8.4 / 10 HIGH source: CNA overview
CWE(s): —
Reserved: 2026-05-13
Published: 2026-05-27 12:16 UTC
Last updated: 2026-05-27 12:16 UTC
Source: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/45xxx/CVE-2026-45885.json
Linked Threat: CVE-2026-45885 — CVE-2026-45885

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:02 UTC
NVD last modified: 2026-06-25 21:13:05 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)

NVD / KEV / EPSS data refreshed 2026-07-27 10:45 UTC. Re-run the 🛰 Backfill from NVD button above to refresh.

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-32351
Assigner: Linux
Published: May 27, 2026, 12:16:57 PM
Updated: May 27, 2026, 12:16:57 PM
EUVD base score: 0.0 / 10
EUVD-reported EPSS: 0.1600
Vendors: Linux
Products: Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a)

Linux (patch: 5.15.202)

Linux (patch: 6.1.165)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <2841bbb5a35c4449c0a0458e8e476b2a62f95147)

Linux (patch: 0)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <e261be6f18929f2397cd54cd583a2df624c129c1)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <2ce2334be155bd8bad6377e99984246ce4dbd08c)

Linux (4.13)

Linux (patch: 6.19.4)

Linux (patch: 6.12.75)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <3ff75cba1c98349a23a8f9333981deba1972cc11)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <cbb9b07f88a9ef6518934c41eb3e8cf840d657d5)

Linux (patch: 7.0)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <642f33e34b969eedec334738fd5df95d2dc42742)

Linux (874b2adbed1253a11549cb9b7b912ab65fea9cf2 <c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4)

Linux (patch: 6.6.128)

Linux (patch: 5.10.252)

Linux (patch: 6.18.14)
Aliases: GHSA-pxv4-rwxf-m755

ENISA description: In the Linux kernel, the following vulnerability has been resolved: power: supply: cpcap-battery: 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 (8)

Affected products (2)

Vendor	Product	Versions	Platforms
Linux	Linux	`874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected), `874b2adbed1253a11549cb9b7b912ab65fea9cf2` (affected)	—
Linux	Linux	`4.13` (affected), `0` (unaffected), `5.10.252` (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 (8)

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

Web references (11)

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/2841bbb5a35c4449c0a0458e8e476b2a62f95147 tenable:git.kernel.org
https://git.kernel.org/stable/c/2ce2334be155bd8bad6377e99984246ce4dbd08c tenable:git.kernel.org
https://git.kernel.org/stable/c/3ff75cba1c98349a23a8f9333981deba1972cc11 tenable:git.kernel.org
https://git.kernel.org/stable/c/642f33e34b969eedec334738fd5df95d2dc42742 tenable:git.kernel.org
https://git.kernel.org/stable/c/c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4 tenable:git.kernel.org
https://git.kernel.org/stable/c/cbb9b07f88a9ef6518934c41eb3e8cf840d657d5 tenable:git.kernel.org
https://git.kernel.org/stable/c/e261be6f18929f2397cd54cd583a2df624c129c1 tenable:git.kernel.org
https://git.kernel.org/stable/c/f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a tenable:git.kernel.org
https://nvd.nist.gov/vuln/detail/CVE-2026-45885 tenable:nvd.nist.gov
https://www.cve.org/CVERecord?id=CVE-2026-45885 tenable:www.cve.org
https://www.first.org/epss/ tenable:www.first.org

NVD-tagged references (8)

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/2841bbb5a35c4449c0a0458e8e476b2a62f95147 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/2ce2334be155bd8bad6377e99984246ce4dbd08c 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/3ff75cba1c98349a23a8f9333981deba1972cc11 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/642f33e34b969eedec334738fd5df95d2dc42742 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/cbb9b07f88a9ef6518934c41eb3e8cf840d657d5 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/e261be6f18929f2397cd54cd583a2df624c129c1 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch

Remediations (18)

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

Microsoft Releases Mitigation for Windows BitLocker Security Bypass 0 ...

web:cybersecuritynews.com

No patch has been released yet; Microsoft has instead issued a multi-step manual mitigation guide while a formal security update is prepared. Windows BitLocker Security Bypass The vulnerability originates in WinRE's handling of the BootExecute registry value under HKLM\ControlSet001\Control\Session Manager.

2026-06-04 00:16 UTC
CVE-2026-45585: Windows Zero-Day Bypasses BitLocker

web:dailysecurityreview.com

Microsoft has disclosed CVE - 2026 -45585, a Windows security feature bypass dubbed "YellowKey," that allows attackers to access BitLocker-protected drives without the encryption key — and no patch is available, leaving organizations reliant on manual workarounds to close the exposure window until a fix is released. The YellowKey Attack Path Through Windows Recovery Environment The ...

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

web:msrc.microsoft.com

Security Update Guide - Microsoft Security Response Center

2026-06-04 00:16 UTC
Nvd - Cve-2026-45585

web:nvd.nist.gov

The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available. Mitigation FAQs Should I leverage the temporary mitigation ?

2026-06-04 00:16 UTC
MC1318295: Mitigation guidance updated with a new script for ... - PUPUWEB

web:pupuweb.com

Microsoft Message Microsoft has updated the mitigation guidance in CVE - 2026 -45585, a Windows BitLocker security feature bypass vulnerability. The updated guidance replaces previously documented manual mitigation steps with a script that helps reduce exposure while a future security update is developed to address this vulnerability.

2026-06-04 00:16 UTC
CVE-2026-45585: YellowKey BitLocker Bypass - socprime.com

web:socprime.com

BitLocker is designed to protect data at rest even when a device is lost, stolen, or powered off, which is why a bypass against that trust model draws immediate attention. The CVE - 2026 -45585 vulnerability, publicly referred to as YellowKey, is a Windows security feature bypass flaw that Microsoft says can let an attacker with physical access sidestep BitLocker protections and access encrypted ...

2026-06-04 00:16 UTC
Microsoft Releases Mitigation for YellowKey BitLocker Bypass CVE-2026-45585

web:vulert.com

CVE - 2026 -45585 is a YellowKey BitLocker security feature bypass affecting Windows 11 and Windows Server 2025. Learn Microsoft's mitigation steps and protection guidance.

2026-06-04 00:16 UTC
Microsoft provides mitigation for "YellowKey" BitLocker bypass flaw ...

web:www.helpnetsecurity.com

Microsoft is working on a fix for CVE - 2026 -45585 (aka "Yellowkey"), a vulnerability that can be used to bypass Windows' BitLocker protection.

2026-06-04 00:16 UTC
From WinRE to SYSTEM: Hunting CVE-2026-45585 Exploitation and the ...

web:www.levelblue.com

At the time of writing, no patch is available, and no CVE has been assigned. Microsoft has since assigned CVE - 2026 -45585 to this issue and released official mitigation guidance, with a security update pending. The vulnerability is classified as a BitLocker Security Feature Bypass requiring physical access.

2026-06-04 00:16 UTC
Microsoft Rolls Out Mitigations for 'YellowKey' BitLocker Bypass

web:www.securityweek.com

Microsoft has announced mitigations for CVE - 2026 -45585, a BitLocker bypass triggered via FsTx in Windows Recovery.

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 - Loading - 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-19 02:27 UTC
Microsoft Patches 59 Vulnerabilities Including Six Actively Exploited ...

web:thehackernews.com

Microsoft patches 59 vulnerabilities, including six actively exploited zero-days, with CISA mandating urgent federal remediation .

2026-06-19 02:27 UTC
Microsoft is working on a patch for 'YellowKey ... - Computerworld

web:www.computerworld.com

Microsoft says it is considering a patch for a zero-day vulnerability, dubbed YellowKey, that allows attackers with access to a Windows device to bypass Bitlocker encryption protection and read ...

2026-06-19 02:27 UTC
Microsoft fixes six zero-days on February 2026 Patch Tuesday

web:www.csoonline.com

Microsoft highlighted six new and actively exploited vulnerabilities among the 60 fixes issued in today's February Patch Tuesday releases.

2026-06-19 02:27 UTC
How To Mitigate The Microsoft Windows BitLocker YellowKey USB 0-Day

web:www.forbes.com

Following the release of a BitLocker zero-day security bypass by a disgruntled hacker, Microsoft has now offered mitigation advice until a patch is available.

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
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-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-45885.json.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/power/supply/cpcap-battery.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "3ff75cba1c98349a23a8f9333981deba1972cc11",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "2ce2334be155bd8bad6377e99984246ce4dbd08c",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "cbb9b07f88a9ef6518934c41eb3e8cf840d657d5",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "2841bbb5a35c4449c0a0458e8e476b2a62f95147",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "e261be6f18929f2397cd54cd583a2df624c129c1",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            },
            {
              "lessThan": "642f33e34b969eedec334738fd5df95d2dc42742",
              "status": "affected",
              "version": "874b2adbed1253a11549cb9b7b912ab65fea9cf2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/power/supply/cpcap-battery.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.13"
            },
            {
              "lessThan": "4.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.252",
              "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.10.252",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.202",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.165",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.128",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.75",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.14",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.4",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "4.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: cpcap-battery: 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:16:57.246Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4"
        },
        {
          "url": "https://git.kernel.org/stable/c/3ff75cba1c98349a23a8f9333981deba1972cc11"
        },
        {
          "url": "https://git.kernel.org/stable/c/2ce2334be155bd8bad6377e99984246ce4dbd08c"
        },
        {
          "url": "https://git.kernel.org/stable/c/cbb9b07f88a9ef6518934c41eb3e8cf840d657d5"
        },
        {
          "url": "https://git.kernel.org/stable/c/f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a"
        },
        {
          "url": "https://git.kernel.org/stable/c/2841bbb5a35c4449c0a0458e8e476b2a62f95147"
        },
        {
          "url": "https://git.kernel.org/stable/c/e261be6f18929f2397cd54cd583a2df624c129c1"
        },
        {
          "url": "https://git.kernel.org/stable/c/642f33e34b969eedec334738fd5df95d2dc42742"
        }
      ],
      "title": "power: supply: cpcap-battery: 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-45885",
    "datePublished": "2026-05-27T12:16:57.246Z",
    "dateReserved": "2026-05-13T15:03:33.082Z",
    "dateUpdated": "2026-05-27T12:16:57.246Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}