CVE-2022-49954 Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag

Medium 5.5 Published Updated

A missing wake-up call in the Linux kernel iforce driver causes a hung task, leading to a local denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2022-49954?

CVE-2022-49954 is a medium-severity denial of service vulnerability in Linux kernel, published on 18 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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().

Which versions are affected by CVE-2022-49954?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2022-49954?

Apply the vendor's patch.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2022-49954 being exploited?

There is no known exploitation of CVE-2022-49954 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as DEBIAN-CVE-2022-49954, GHSA-vq44-q98p-r6hq, UBUNTU-CVE-2022-49954.

Is CVE-2022-49954 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free