Local system hang via recursive device locking
Published Feb 26, 2025 · Updated May 11, 2026
Improper locking in affected Linux kernel releases allows local users to hang the system during asynchronous device probing. __device_attach holds the device lock while scheduling __device_attach_async_helper, but the synchronous fallback calls that helper and attempts to acquire the same lock again. Low-privileged local access and either memory-allocation failure or exhaustion of the asynchronous work limit are required; the bounded consequence is a device-attachment hang.
Summary
What happened
Improper locking in affected Linux kernel releases allows local users to hang the system during asynchronous device probing. __device_attach holds the device lock while scheduling __device_attach_async_helper, but the synchronous fallback calls that helper and attempts to acquire the same lock again. Low-privileged local access and either memory-allocation failure or exhaustion of the asynchronous work limit are required; the bounded consequence is a device-attachment hang.
The record
- CVE
- CVE-2022-49371
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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=4.2
- Affected versionversion=765230b5f084863183aa8adb3405ab3f32c0b16e <34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e
- Affected versionversion=765230b5f084863183aa8adb3405ab3f32c0b16e <36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada
- Affected versionversion=765230b5f084863183aa8adb3405ab3f32c0b16e <593b595332bd2d65e1a5c1ae7897996c157f5468
- Affected versionversion=765230b5f084863183aa8adb3405ab3f32c0b16e <b232b02bf3c205b13a26dcec08e53baddd8e59ed
- Affected versionversion=765230b5f084863183aa8adb3405ab3f32c0b16e <d53a227bfcd5160ce1b61d9954901968a20651e7
- Affected versionversion=765230b5f084863183aa8adb3405ab3f32c0b16e <df6de52b80aa3b46f5ac804412355ffe2e1df93e
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.
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