ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-99215

CVE-2026-99215: power: supply: core: prevent unregistering a power supply while a callback runs

Published Oct 28, 2026 · catalog updated Oct 29, 2026 · Linux Linux

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-99215. EPSS is 0.16%. Act only if a listed version of Linux Linux is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.16%
Remediation
Advisory link
Affected products
Debian:12 linux · Debian:13 linux · Debian:14 linux · Linux Kernel · linux kernel · vendor Linux Linux

In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from other contexts, such as external_power_changed() triggered by the TCPM stack. If a power supply is unregistered while the callback is still running, the driver data can already be freed when the callback tries to access it, leading to a use-after-free. This happens e.g. when the hardware bus carrying the power supply device malfunctions (e.g. I2C is hogged down by another malfunctioning device) immediately after the power supply is registered, and thus the core is still processing the callbacks which were queued up when the driver starts the removal, leading in some cases to a kernel crash, e.g.: [ 11.645942] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000005 [ 11.646751] Mem abort info: [ 11.647006] ESR = 0x0000000096000004 [ 11.647338] EC = 0x25: DABT (current EL), IL = 32 bits [ 11.647806] SET = 0, FnV = 0 [ 11.648077] EA = 0, S1PTW = 0 [ 11.648356] FSC = 0x04: level 0 translation fault [ 11.648785] Data abort info: [ 11.649041] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 11.649524] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 11.649981] GCS = 0, Overlay = 0, DirtyBit = 0 [ 11.650390] [0000000000000005] user address but active_mm is swapper [ 11.650955] Internal error: Oops: 0000000096000004 [#1] SMP [ 11.651460] Modules linked in: [ 11.651742] CPU: 1 UID: 0 PID: 144 Comm: kworker/1:2 Not tainted 7.2.0-rc6-g62a9297af2cd #1 PREEMPT [ 11.652553] Hardware name: Flipper One rev. F0B1C2 (DT) [ 11.653024] Workqueue: events power_supply_changed_work [ 11.653511] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 11.654135] pc : __power_supply_is_supplied_by+0x18/0x100 [ 11.654624] lr : __power_supply_am_i_supplied+0x40/0xb8 [ 11.655098] sp : ffff80008192bb30 [ 11.655399] x29: ffff80008192bb30 x2

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:12 linux6.1.106-1, 6.1.106-2, 6.1.106-3
  • Debian:13 linux6.12.100-1, 6.12.101-1, 6.12.105-1
  • Debian:14 linux6.12.100-1, 6.12.101-1, 6.12.105-1
  • Linux Kernel4.1.0 → 6.18.59; 6.19.0 → 7.2.13
  • linux kernelversion unspecified
  • vendor Linux Linuxversion unspecified

How to fix CVE-2026-99215

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-99215. EPSS is 0.16%. Act only if a listed version of Linux Linux is installed.

Which versions are affected?

Compare what you have installed with Kernel 4.1.0 → 6.18.59; 6.19.0 → 7.2.13. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.16%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Debian security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 28, 2026 · Tenable CVE Database

    Detected

    In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from other contexts, such as external_power_changed() triggered by the TCPM stack. If a power supply is unregistered while the callback is still running, the driver data can

  2. Oct 28, 2026 · Trivy Vulnerability DB

    Updated

    In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from other contexts, such as external_power_changed() triggered by the TCPM stack. If a power supply is unregistered while the callback is still running, the driver data can

  3. Oct 29, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    Kernel fixed in 6.18.59; Kernel fixed in 7.2.13

  4. Oct 29, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    Kernel fixed in 6.18.59; 6.19.0

  5. Oct 29, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from other contexts, such as external_power_changed() triggered by the TCPM stack. If a power supply is unregistered while the callback is still running, the driver data can

Sources

  • BSI CERT-BundGovernment advisoryCVE-2026-99215

    Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

    wid.cert-bund.de
  • CVE.orgVulnerability recordCVE-2026-99215

    In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from other contexts, such as external_power_changed()

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-99215

    30-day exploitation probability 0.16%

    first.org
  • Linux Kernel CVEVendor advisoryCVE-2026-99215

    From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from

    git.kernel.org
  • OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-99215

    power: supply: core: prevent unregistering a power supply while a callback runs

    osv.dev
  • Tenable CVE DatabaseVulnerability recordCVE-2026-99215

    In the Linux kernel, the following vulnerability has been resolved: power: supply: core: prevent unregistering a power supply while a callback runs Once a power supply is registered, its callbacks can immediately start firing from other contexts, such as external_power_changed() triggered by the TCPM stack. If a power supply is unregistered while the callback is still running, the driver data can

    tenable.com
  • Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-99215
    osv.dev

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 7, 2026
  • BSI CERT-BundOct 30, 2026
  • OpenSSF OSV / OSV ScannerOct 29, 2026
  • CVE.orgOct 28, 2026
  • Trivy Vulnerability DBOct 28, 2026
  • Linux Kernel CVEOct 28, 2026
  • Tenable CVE DatabaseOct 28, 2026