Kernel crash via unchecked allocation result
Published Dec 14, 2022 · Updated Apr 22, 2025
NULL pointer dereference in Linux Kernel through 5.16-rc6 allows local users to crash the kernel through LKDTM array-bounds testing. The lkdtm_ARRAY_BOUNDS function dereferences buffers returned by kmalloc without first checking whether either allocation returned NULL. A local user must be able to invoke the LKDTM ARRAY_BOUNDS test; exploitation interrupts service without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux Kernel through 5.16-rc6 allows local users to crash the kernel through LKDTM array-bounds testing. The lkdtm_ARRAY_BOUNDS function dereferences buffers returned by kmalloc without first checking whether either allocation returned NULL. A local user must be able to invoke the LKDTM ARRAY_BOUNDS test; exploitation interrupts service without reported data disclosure or modification.
The record
- CVE
- CVE-2022-3104
- Published
- Dec 14, 2022
- Updated
- Apr 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- 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.
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