Kernel driver crash via unchecked RGB row length
Published May 20, 2022 · Updated Nov 3, 2025
Buffer overflow in OpenRazer 3.3.0 and earlier allows local users to crash the razerkbd kernel driver via matrix_custom_frame. The custom-frame handler derives row_length from attacker-controlled start and stop columns, then memcpy copies that length into an 80-byte arguments array without a bounds check. Exploitation requires write access to the device sysfs attribute; the demonstrated result is a driver crash, while kernel code execution also requires an information leak and absent FORTIFY_SOURCE.
Summary
What happened
Buffer overflow in OpenRazer 3.3.0 and earlier allows local users to crash the razerkbd kernel driver via matrix_custom_frame. The custom-frame handler derives row_length from attacker-controlled start and stop columns, then memcpy copies that length into an 80-byte arguments array without a bounds check. Exploitation requires write access to the device sysfs attribute; the demonstrated result is a driver crash, while kernel code execution also requires an information leak and absent FORTIFY_SOURCE.
The record
- CVE
- CVE-2022-29021
- Published
- May 20, 2022
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
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
- matrix_custom_frame driver-crash proof of conceptproof of concept · demonstrated
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