Kernel hang via unchecked nested USB reset
Published Jun 18, 2025 · Updated May 11, 2026
Denial of service in the Linux USB core allows local users to hang reset processing by removing a device during an existing reset. While rtl8712 is unbound from a composite device, r871xu_dev_remove calls usb_reset_device, and the USB core starts a nested reset without checking whether one is already in progress. Reachability requires local low-privileged access and the affected rtl8712 composite-device path; recursive interface-mutex acquisition stalls reset work.
Summary
What happened
Denial of service in the Linux USB core allows local users to hang reset processing by removing a device during an existing reset. While rtl8712 is unbound from a composite device, r871xu_dev_remove calls usb_reset_device, and the USB core starts a nested reset without checking whether one is already in progress. Reachability requires local low-privileged access and the affected rtl8712 composite-device path; recursive interface-mutex acquisition stalls reset work.
The record
- CVE
- CVE-2022-49936
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 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=2.6.27
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <1b29498669914c7f9afb619722421418a753d372
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <9c6d778800b921bde3bff3cff5003d1650f942d1
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <abe3cfb7a7c8e907b312c7dbd7bf4d142b745aa8
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <c548b99e1c37db6f7df86ecfe9a1f895d6c5966e
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <cc9a12e12808af178c600cc485338bac2e37d2a8
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <d5eb850b3e8836197a38475840725260b9783e94
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <d90419b8b8322b6924f6da9da952647f2dadc21b
- Affected versionversion=78d9a487ee961c356e1a934d9a92eca38ffb3a70 <df1875084898b15cbc42f712e93d7f113ae6271b
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