Service interruption via leaked Hyper-V HID device
Published May 1, 2025 · Updated May 11, 2026
Memory leak in Linux 3.3 through 6.1-rc4 allows local users to interrupt service through failed Hyper-V mouse device registration. In mousevsc_probe(), the error path after hid_add_device() fails omits hid_destroy_device(), leaving the hid_dev allocation unreleased. Reachability requires the Hyper-V HID driver and a device-registration failure; the bounded consequence is retained kernel memory and eventual service interruption.
Summary
What happened
Memory leak in Linux 3.3 through 6.1-rc4 allows local users to interrupt service through failed Hyper-V mouse device registration. In mousevsc_probe(), the error path after hid_add_device() fails omits hid_destroy_device(), leaving the hid_dev allocation unreleased. Reachability requires the Hyper-V HID driver and a device-registration failure; the bounded consequence is retained kernel memory and eventual service interruption.
The record
- CVE
- CVE-2022-49874
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 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=3.3
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <249b743801c00542e9324f87b380032e957a43e8
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <5ad95d71344b7ffec360d62591633b3c465dc049
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <5f3aba6566b866f5b0a4916f0b2e8a6ae66a6451
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <8597b59e3d22b27849bd3e4f92a3d466774bfb04
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <a6d2fb1874c52ace1f5cf1966ee558829c5c19b6
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <b5bcb94b0954a026bbd671741fdb00e7141f9c91
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <e29289d0d8193fca6d2c1f0a1de75cfc80edec00
- Affected versionversion=74c4fb058083b47571a4f76dcfce95085f2d8098 <ed75d1a1c31a0cae8ecc8bcea710b25c0be68da0
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