LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-49954 is a Linux kernel reliability flaw in the iforce input driver. A device close path can wait indefinitely because a wake-up was missed after clearing a transmit-running flag. The source describes a hung task, not data theft or remote compromise.

Executive priority

Treat as a targeted availability and stability issue, not an emergency based on the supplied evidence. Patch through normal kernel maintenance unless affected systems depend on input-device reliability or show related hung-task symptoms.

Technical view

The iforce driver could block in iforce_close() at wait_event_interruptible() while holding dev->mutex, preventing input_disconnect_device() during __input_unregister_device(). The kernel fix adds a helper that clears IFORCE_XMIT_RUNNING and calls wake_up_all().

Likely exposure

Exposure appears limited to Linux systems with affected kernels and the iforce input driver path. The source lists Linux kernel versions and stable commits but provides no CPEs, CVSS, distribution package mapping, or reachability details.

Exploitation context

No cited source says this is actively exploited. KEV is false. The source evidence is a syzbot hung-task report and kernel fix description; attacker requirements and practical exploitability are not described.

Researcher notes

The vulnerability is a synchronization bug: clear_bit() occurred without waking waiters. The bundle does not provide CVSS, CWE, CPEs, exploit details, or distribution advisories, so exposure validation depends on kernel lineage and vendor packaging.

Mitigation direction

  • Apply the relevant Linux stable kernel update containing the referenced iforce fix.
  • Check your distribution kernel advisory for package-specific fixed versions.
  • Prioritize systems using force-feedback input devices or loading the iforce driver.
  • Monitor for vendor guidance if your kernel branch is not represented in the references.

Validation and detection

  • Inventory running kernel versions and compare them with vendor fixed-kernel advisories.
  • Check whether the iforce driver is present or loadable on relevant systems.
  • Review kernel logs for hung tasks involving iforce_close or input device unregister paths.
  • Confirm updated kernels include one of the referenced stable fixes.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49954 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc2b27ef672992a206e5b221b8676972dd840ffa5, c2b27ef672992a206e5b221b8676972dd840ffa5, c2b27ef672992a206e5b221b8676972dd840ffa5, c2b27ef672992a206e5b221b8676972dd840ffa5, c2b27ef672992a206e5b221b8676972dd840ffa5unaffected
LinuxLinux2.6.33, 0, 5.4.213, 5.10.142, 5.15.66, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.