Kernel crash via unchecked error pointer
Published Mar 1, 2023 · Updated Mar 19, 2025
A pointer-checking flaw in Linux kernel memory-tier initialization before 6.2 allows local users to cause a kernel crash. memory_tier_init treats an error pointer returned by alloc_memory_type as a valid allocation because it checks for NULL instead of IS_ERR. The path requires alloc_memory_type to fail during initialization, and SUSE disputes exploitability because no realistic user-controlled route to that error case is known.
Summary
What happened
A pointer-checking flaw in Linux kernel memory-tier initialization before 6.2 allows local users to cause a kernel crash. memory_tier_init treats an error pointer returned by alloc_memory_type as a valid allocation because it checks for NULL instead of IS_ERR. The path requires alloc_memory_type to fail during initialization, and SUSE disputes exploitability because no realistic user-controlled route to that error case is known.
The record
- CVE
- CVE-2023-23005
- Published
- Mar 1, 2023
- Updated
- Mar 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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.
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