CVE-2022-49954
MediumIn 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 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
2.6.33
and later are affected. Fixed in
5.4.213,
5.10.142,
5.15.66,
5.19.8,
6.0
and their respective stable series.
References
5 total-
Patch
-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2022-49954?
CVE-2022-49954 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 2.6.33 onward and has been patched in 5.4.213, 5.10.142, 5.15.66 and others. CVE-2022-49954 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2022-49954?
CVE-2022-49954 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2022-49954?
Yes. CVE-2022-49954 has been patched. Fixed versions include 5.4.213, 5.10.142, 5.15.66 and others. If you are running Linux kernel 2.6.33 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-49954 actively exploited?
No. CVE-2022-49954 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.