Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 98e01215708b6d416345465c09dce2bd4868c67a, Kernel b271090eea3899399e2adcf79c9c95367d472b03, Kernel b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.33, >=c2b27ef672992a206e5b221b8676972dd840ffa5 <98e01215708b6d416345465c09dce2bd4868c67a, >=c2b27ef672992a206e5b221b8676972dd840ffa5 <b271090eea3899399e2adcf79c9c95367d472b03, >=c2b27ef672992a206e5b221b8676972dd840ffa5 <b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c, >=c2b27ef672992a206e5b221b8676972dd840ffa5 <d186c65599bff0222da37b9215784ddfe39f9e1b, >=c2b27ef672992a206e5b221b8676972dd840ffa5 <df1b53bc799d58f79701c465505a206c72ad4ab8 | 98e01215708b6d416345465c09dce2bd4868c67a, b271090eea3899399e2adcf79c9c95367d472b03, b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c, d186c65599bff0222da37b9215784ddfe39f9e1b, df1b53bc799d58f79701c465505a206c72ad4ab8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket