CVE-2022-49954
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-18

Last updated on: 2025-11-14

Assigner: kernel.org

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-18
Last Modified
2025-11-14
Generated
2026-05-07
AI Q&A
2025-06-18
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 14 associated CPEs
Vendor Product Version / Range
linux linux_kernel 2.6.33
linux linux_kernel 2.6.33
linux linux_kernel 2.6.33
linux linux_kernel 2.6.33
linux linux_kernel 2.6.33
linux linux_kernel 2.6.33
linux linux_kernel 2.6.33
linux linux_kernel 6.0
linux linux_kernel 6.0
linux linux_kernel 6.0
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel involves the iforce input driver where a wake_up() call was missing after clearing the IFORCE_XMIT_RUNNING flag. This omission causes a hung task situation during device closure, specifically in iforce_close(), which waits indefinitely with a mutex held, blocking device unregistration. The issue was fixed by introducing a helper function that clears the flag and then calls wake_up_all() to properly wake waiting tasks.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to hang or become unresponsive when closing an iforce input device, due to tasks waiting indefinitely while holding a mutex. This can lead to system instability or degraded performance when using affected input devices.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability is fixed by applying a patch that introduces a helper function which calls clear_bit() followed by wake_up_all() to ensure proper wake-up after clearing the IFORCE_XMIT_RUNNING flag. Immediate mitigation involves updating the Linux kernel to a version that includes this fix.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart