Memory corruption via uncanceled charger removal work
Published Sep 17, 2026 · Updated Sep 17, 2026
Use-after-free in Linux's sc2731_charger driver allows local users to corrupt kernel memory during driver removal. The remove path unregisters the USB notifier but leaves queued or running info->work able to access driver data after its managed allocation is released. Exposure requires the affected charger driver and overlapping work during teardown; Amazon Linux assesses high privileges as necessary, and no specific crash or privilege-escalation outcome is documented.
Summary
What happened
Use-after-free in Linux's sc2731_charger driver allows local users to corrupt kernel memory during driver removal. The remove path unregisters the USB notifier but leaves queued or running info->work able to access driver data after its managed allocation is released. Exposure requires the affected charger driver and overlapping work during teardown; Amazon Linux assesses high privileges as necessary, and no specific crash or privilege-escalation outcome is documented.
The record
- CVE
- CVE-2026-90394
- 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=5.0
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <05c188addc6d1af51e28496e95096f4df9a000e9
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <232e9e946b496e4706e2f34ce4a617460d8ae713
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <972d88069050d0272b776145b824198b8f899dce
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <aab9d81a415c6653b44b057695ebfbba34dc9556
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <bb74a5ab30963022981381ea6aee176fd0c7957c
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <c6df6e0c099086bc553d44410015cc81795070e6
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <d5266b4c5c77152e386a3a2d9d5244b3b6cbd57a
- Affected versionversion=8ac1091ed18b4a6cb0dc2cd5653f080736f89392 <dfc859bb8d332c525872f1a44028137724fa1998
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