Kernel crash via zero-pad camera descriptor
Published Sep 18, 2025 · Updated Sep 18, 2025
Improper input validation in affected Linux kernel releases before 6.3 allows local users to crash the kernel via malformed camera descriptors. uvc_mc_create_links() accepts a source entity with zero pads and then selects pad metadata from that empty array while constructing media links. Reachability requires low-privilege local access and a camera exposing the invalid entity graph; the resulting invalid pad access interrupts the host.
Summary
What happened
Improper input validation in affected Linux kernel releases before 6.3 allows local users to crash the kernel via malformed camera descriptors. uvc_mc_create_links() accepts a source entity with zero pads and then selects pad metadata from that empty array while constructing media links. Reachability requires low-privilege local access and a camera exposing the invalid entity graph; the resulting invalid pad access interrupts the host.
The record
- CVE
- CVE-2023-53437
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <11196ee3916e50a5da3c1e6ecda19a02dca14ba3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1a76cfc388cf105d3e04ac592670a52a3864b1ba
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2914259fcea23971c6fed8b2618d3a729a78c365
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <31a8d11d28b57656cebfbd4c0b8b76f6ad5b017d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <41ddb251c68ac75c101d3a50a68c4629c9055e4c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4e4e6ca62e77539d4df8d13137e2683b10baddd9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8f4a424af5879baefb0fb8a8a09b09ea1779483
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d8aa2e1ae6426d7cbddf1735aed1a63ddf0e6909
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