Stale-state access via unsynchronized driver teardown
Published Sep 17, 2026 · Updated Sep 17, 2026
A teardown race in Linux's isp1704_charger driver allows local users to access stale power-supply state via driver removal. The isp1704_charger_remove function tears down the power supply without waiting for work scheduled by USB notifications or initial VBUS detection, leaving that work accessing removed state. Exposure requires an active driver on supported ISP170x hardware and work overlapping privileged local removal; public sources do not establish a specific crash or privilege-escalation outcome.
Summary
What happened
A teardown race in Linux's isp1704_charger driver allows local users to access stale power-supply state via driver removal. The isp1704_charger_remove function tears down the power supply without waiting for work scheduled by USB notifications or initial VBUS detection, leaving that work accessing removed state. Exposure requires an active driver on supported ISP170x hardware and work overlapping privileged local removal; public sources do not establish a specific crash or privilege-escalation outcome.
The record
- CVE
- CVE-2026-90395
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.37
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <1ed74e3a8bbc104b744c257f8cbb2c371485ba4f
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <60c5b8a9ef4dbc5d69bbc1a960fe55826cb3b643
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <a4750d5d7d1a3bac1b23ac5817f2bfbedcc95ac7
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <ad4f4e6678ecd4f6de97b73d4bab7d2352d40d70
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <b0fa49bcb25b905b49dbb681c8a94f00d1a7f94d
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <c22a9a539c76179fca5c0f28ee7652c4afda750b
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <cb442f1823df5782002ab4c36a8775270d41a772
- Affected versionversion=ec46475f3e3163dd80bfee086fa71b36455ecc0b <f312c5d17f2a7ad50df5b52935d76abbe7b89feb
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started