Service interruption via uninitialized idmouse image buffer
Published Dec 24, 2025 · Updated Dec 24, 2025
Uninitialized memory use in the Linux kernel idmouse driver allows local users to interrupt service through a failing USB command. When any ftip_command call fails, idmouse_create_image reaches its reset path with bulk_in_buffer image bytes unset, then dereferences them during image validation. Reachability requires low-privilege local access and an attached USB device handled by idmouse; published assessments limit the impact to availability.
Summary
What happened
Uninitialized memory use in the Linux kernel idmouse driver allows local users to interrupt service through a failing USB command. When any ftip_command call fails, idmouse_create_image reaches its reset path with bulk_in_buffer image bytes unset, then dereferences them during image validation. Reachability requires low-privilege local access and an attached USB device handled by idmouse; published assessments limit the impact to availability.
The record
- CVE
- CVE-2022-50733
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 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 <1eae30c0113dde7522088231584d62415011a035
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <20b8c456df584ebb2387dc23d40ebe4ff334417c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6163a5ae097bc78fa26c243fb384537e25610fd7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7dad42032f68718259590b0cc7654e9a95ff9762
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <adad163d1cff248a5df9f7cec50158e6ca89f33b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b3304a6df957cc89a0590cb505388d659bf3db4c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b8bbae3236ab7dccc66c42bc3f7cdbcfc0786e54
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bce2b0539933e485d22d6f6f076c0fcd6f185c4c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f589b667567fde4f81d6e6c40f42b9f2224690ea
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