Quick answers
- Is CVE-2026-99215 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99215 being exploited in the wild.
- How severe is CVE-2026-99215?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Linux Linux kernel.
- Is there a fix for CVE-2026-99215?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-99215 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-99215?
- Check whether you run Linux Kernel. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free vulnerability exists in the power supply core when unregistering a power supply during active callback execution from other contexts like the TCPM stack. The vulnerability occurs because driver data can be freed while external_power_changed() callbacks are still running. The fix introduces a read-write semaphore between external_power_changed() and power_supply_unregister() to prevent premature data deallocation.
Affected products
- Linux Linux kernel
Timeline
- 2026-10-28: disclosed