CVE-2022-49954Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected c2b27ef672992a206e5b221b8676972dd840ffa5 – < d186c65599bff0222da37b9215784ddfe39f9e1b
- affected c2b27ef672992a206e5b221b8676972dd840ffa5 – < b271090eea3899399e2adcf79c9c95367d472b03
- affected c2b27ef672992a206e5b221b8676972dd840ffa5 – < df1b53bc799d58f79701c465505a206c72ad4ab8
- affected c2b27ef672992a206e5b221b8676972dd840ffa5 – < b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c
- affected c2b27ef672992a206e5b221b8676972dd840ffa5 – < 98e01215708b6d416345465c09dce2bd4868c67a
- affected 2.6.33
- unaffected < 2.6.33
- unaffected 5.4.213 – ≤ 5.4.*
- unaffected 5.10.142 – ≤ 5.10.*
- unaffected 5.15.66 – ≤ 5.15.*
- unaffected 5.19.8 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References
References5
- https://git.kernel.org/stable/c/d186c65599bff0222da37b9215784ddfe39f9e1b (opens in a new tab)
- https://git.kernel.org/stable/c/b271090eea3899399e2adcf79c9c95367d472b03 (opens in a new tab)
- https://git.kernel.org/stable/c/df1b53bc799d58f79701c465505a206c72ad4ab8 (opens in a new tab)
- https://git.kernel.org/stable/c/b533b9d3a0d1327cbb31c201dc8dbbf98c8bfe3c (opens in a new tab)
- https://git.kernel.org/stable/c/98e01215708b6d416345465c09dce2bd4868c67a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55236 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49954)Record last updated .