Bug 2373565 (CVE-2022-49954) - CVE-2022-49954 kernel: Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
Summary: CVE-2022-49954 kernel: Input: iforce - wake up after clearing IFORCE_XMIT_RUN...
Keywords:
Status: NEW
Alias: CVE-2022-49954
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-18 12:08 UTC by OSIDB Bzimport
Modified: 2025-06-19 11:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-06-18 12:08:35 UTC
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().

Comment 1 Avinash Hanwate 2025-06-19 11:26:56 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025061811-CVE-2022-49954-97f4@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.