What’s Vulnerable › Vulnerabilities
CVE-2022-49954: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2025-06-18 · updated 2026-06-17
Description
In the Linux kernel, the following vulnerability has been resolved: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev->mutex held is blocking input_disconnect_device() from __input_unregister_device(). It seems that the cause is simply that commit c2b27ef672992a20 ("Input: iforce - wait for command completion when closing the device") forgot to call wake_up() after clear_bit(). Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().
Affected products
- Linux kernel: from 2.6.34 before 5.4.213; from 5.5 before 5.10.142; from 5.11 before 5.15.66; from 5.16 before 5.19.8; 2.6.33, 2.6.33-rc3, 2.6.33-rc4, 2.6.33-rc5, 2.6.33-rc6, 2.6.33-rc7 (+4) — fixed in 5.10.142, 5.15.66, 5.19.8, 5.4.213
How to fix
Upgrade to a fixed version: Linux kernel 5.10.142, 5.15.66, 5.19.8, 5.4.213. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/98e01215708b6d416345465c09dce2bd4868c67a
- https://git.kernel.org/stable/c/b271090eea3899399e2adcf79c9c95367d472b03
- https://git.kernel.org/stable/c/b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c
- https://git.kernel.org/stable/c/d186c65599bff0222da37b9215784ddfe39f9e1b
- https://git.kernel.org/stable/c/df1b53bc799d58f79701c465505a206c72ad4ab8
Get alerted when CVE-2022-49954 or the next vulnerability affects your stack