Invalid memory access via retained panic notifier
Published Sep 17, 2026 · Updated Sep 17, 2026
Use-after-free in the cros_ec_debugfs driver in Linux 6.3 allows local users to trigger invalid memory access via EC panic events. The remove path releases debugfs and console-log state without unregistering notifier_panic, leaving a callback that queues work against released data. Triggering requires driver removal followed by an EC panic notification; SUSE assesses administrative privileges and availability-only impact, but the precise crash or hang outcome is not published.
Summary
What happened
Use-after-free in the cros_ec_debugfs driver in Linux 6.3 allows local users to trigger invalid memory access via EC panic events. The remove path releases debugfs and console-log state without unregistering notifier_panic, leaving a callback that queues work against released data. Triggering requires driver removal followed by an EC panic notification; SUSE assesses administrative privileges and availability-only impact, but the precise crash or hang outcome is not published.
The record
- CVE
- CVE-2026-90404
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- 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=6.3
- Affected versionversion=d90fa2c64d59f5f151beeef5dbc599784b3391ca <05c1081ae4503e45b934b390350f942db3208892
- Affected versionversion=d90fa2c64d59f5f151beeef5dbc599784b3391ca <56989e2a9c292ff7689603feed41d030301ca636
- Affected versionversion=d90fa2c64d59f5f151beeef5dbc599784b3391ca <a5d3128b06ccfc398c2e456fddebadce52310bd8
- Affected versionversion=d90fa2c64d59f5f151beeef5dbc599784b3391ca <e2cbe14361d7cb0b5abd66d87f3afa0e16efde9f
- Affected versionversion=d90fa2c64d59f5f151beeef5dbc599784b3391ca <e5954d3031fb55dd31aa59bae477d63c68e941c0
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
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