Vulnerability 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().
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.34, < 5.4.213 |
References
- https://git.kernel.org/stable/c/98e01215708b6d416345465c09dce2bd4868c67aPatch
- https://git.kernel.org/stable/c/b271090eea3899399e2adcf79c9c95367d472b03Patch
- https://git.kernel.org/stable/c/b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3cPatch
- https://git.kernel.org/stable/c/d186c65599bff0222da37b9215784ddfe39f9e1bPatch
- https://git.kernel.org/stable/c/df1b53bc799d58f79701c465505a206c72ad4ab8Patch
FAQ
What is CVE-2022-49954?
CVE-2022-49954 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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], ...
How severe is CVE-2022-49954?
CVE-2022-49954 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-49954?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.