Kernel crash via unchecked matrix frame length
Published May 20, 2022 · Updated Nov 3, 2025
Buffer overflow in OpenRazer 3.3.0 and earlier allows local users to crash the kernel through the razeraccessory matrix_custom_frame interface. The matrix custom-frame functions derive row_length from attacker-controlled column bounds and copy that many RGB bytes into fixed-size report arguments without capping the length. Exploitation requires local write access to the driver attribute; the disclosed outcome is a kernel crash, while privilege escalation was not demonstrated under fortified memcpy bounds checking.
Summary
What happened
Buffer overflow in OpenRazer 3.3.0 and earlier allows local users to crash the kernel through the razeraccessory matrix_custom_frame interface. The matrix custom-frame functions derive row_length from attacker-controlled column bounds and copy that many RGB bytes into fixed-size report arguments without capping the length. Exploitation requires local write access to the driver attribute; the disclosed outcome is a kernel crash, while privilege escalation was not demonstrated under fortified memcpy bounds checking.
The record
- CVE
- CVE-2022-29022
- Published
- May 20, 2022
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 20, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 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