https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 03:31:42 +0000 https://vulnerability.circl.lu/vuln/cve-2022-49954 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p> <p>syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device().</p> <p>It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit().</p> <p>Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag</p> <p>syzbot is reporting hung task at __input_unregister_device() [1], for iforce_close() waiting at wait_event_interruptible() with dev-&gt;mutex held is blocking input_disconnect_device() from __input_unregister_device().</p> <p>It seems that the cause is simply that commit c2b27ef672992a20 (&#34;Input: iforce - wait for command completion when closing the device&#34;) forgot to call wake_up() after clear_bit().</p> <p>Fix this problem by introducing a helper that calls clear_bit() followed by wake_up_all().</p> https://vulnerability.circl.lu/vuln/cve-2022-49954