Local system crash via unreleased charger interrupt
Published Dec 14, 2022 · Updated Apr 22, 2025
NULL pointer dereference in Linux Kernel 5.16-rc6 and earlier allows local users to crash the system through the WM8350 charger driver. The free_charger_irq() teardown path omits release of the WM8350_IRQ_CHG_FAST_RDY interrupt registered by wm8350_init_charger(), leaving inconsistent IRQ state that leads to a null pointer dereference. Low-privileged local access and a system using the WM8350 charger driver are required; the reported consequence is a system crash.
Summary
What happened
NULL pointer dereference in Linux Kernel 5.16-rc6 and earlier allows local users to crash the system through the WM8350 charger driver. The free_charger_irq() teardown path omits release of the WM8350_IRQ_CHG_FAST_RDY interrupt registered by wm8350_init_charger(), leaving inconsistent IRQ state that leads to a null pointer dereference. Low-privileged local access and a system using the WM8350 charger driver are required; the reported consequence is a system crash.
The record
- CVE
- CVE-2022-3111
- Published
- Dec 14, 2022
- Updated
- Apr 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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=Linux 5.16-rc6
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo