Local system crash via incorrect error-pointer test
Published Mar 1, 2023 · Updated Mar 20, 2025
NULL pointer dereference in Linux kernel before 5.16.3 allows local users to crash the system through the MediaTek UFS driver. In ufs_mtk_init_va09_pwr_ctrl(), a NULL test accepts regulator_get()'s error pointer as valid and enables VA09 power-control operations on it. Reachability requires the MediaTek UFS VA09 path and a failed regulator lookup; public sources do not identify the local action that triggers that failure.
Summary
What happened
NULL pointer dereference in Linux kernel before 5.16.3 allows local users to crash the system through the MediaTek UFS driver. In ufs_mtk_init_va09_pwr_ctrl(), a NULL test accepts regulator_get()'s error pointer as valid and enables VA09 power-control operations on it. Reachability requires the MediaTek UFS VA09 path and a failed regulator lookup; public sources do not identify the local action that triggers that failure.
The record
- CVE
- CVE-2023-23001
- Published
- Mar 1, 2023
- Updated
- Mar 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 20, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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