Local crash via unchecked vivid ioctl arithmetic
Published Feb 6, 2023 · Updated Mar 25, 2025
Improper input validation in Linux kernel 6.2-rc6 allows local users to crash systems through V4L2 vivid-driver ioctls. The vivid test driver divides by an unchecked user-supplied timing value, overflows 32-bit frame-buffer size arithmetic before a later memory copy, and leaks memory. The vivid driver must be built and exposed as /dev/videoX; distributions that omit its configuration are unaffected.
Summary
What happened
Improper input validation in Linux kernel 6.2-rc6 allows local users to crash systems through V4L2 vivid-driver ioctls. The vivid test driver divides by an unchecked user-supplied timing value, overflows 32-bit frame-buffer size arithmetic before a later memory copy, and leaks memory. The vivid driver must be built and exposed as /dev/videoX; distributions that omit its configuration are unaffected.
The record
- CVE
- CVE-2023-0615
- Published
- Feb 6, 2023
- Updated
- Mar 25, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-20, CWE-369, CWE-401, CWE-190, T1529
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2023CVE publishedPublication date reported by the CVE source.
- Mar 25, 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 kernel 6.2-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.
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