System crash via unchecked CEC receive length
Published Jan 2, 2025 · Updated May 11, 2026
Out-of-bounds write in the Linux kernel 4.8 through 6.1-rc1 allows local users to crash the system via an oversized CEC message. The s5p_cec interrupt handler copies a length from the receive-status register into cec->msg.len and, before the fix, passes values above the 16-byte CEC limit to s5p_cec_get_rx_buf without clamping them. Reachability requires the Samsung S5P CEC driver and CEC-capable hardware; an oversized reported receive length can corrupt kernel memory and interrupt the system.
Summary
What happened
Out-of-bounds write in the Linux kernel 4.8 through 6.1-rc1 allows local users to crash the system via an oversized CEC message. The s5p_cec interrupt handler copies a length from the receive-status register into cec->msg.len and, before the fix, passes values above the 16-byte CEC limit to s5p_cec_get_rx_buf without clamping them. Reachability requires the Samsung S5P CEC driver and CEC-capable hardware; an oversized reported receive length can corrupt kernel memory and interrupt the system.
The record
- CVE
- CVE-2022-49035
- Published
- Jan 2, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-770, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 2, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <1609231f86760c1f6a429de7913dd795b9faa08c
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <2654e785bd4aa2439cdffbe7dc1ea30a0eddbfe4
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <4a449430ecfb199b99ba58af63c467eb53500b39
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <7ccb40f26cbefa1c6dfd3418bea54c9518cdbd8a
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <93f65ce036863893c164ca410938e0968964b26c
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <a2728bf9b6c65e46468c763e3dab7e04839d4e11
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <cbfa26936f318b16ccf9ca31b8e8b30c0dc087bd
- Affected versionversion=1bcbf6f4b6b050eaf8f1fb1adf5c4779a3623c5b <fc0f76dd5f116fa9291327024dda392f8b4e849c
- Affected versionversion=4.8
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.
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