CVE-2022-49790
Input: iforce - invert valid length check when fetching device IDs
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: Input: iforce - invert valid length check when fetching device IDs syzbot is reporting uninitialized value at iforce_init_device() [1], for commit 6ac0aec6b0a6 ("Input: iforce - allow callers supply data buffer when fetching device IDs") is checking that valid length is shorter than bytes to read. Since iforce_get_id_packet() stores valid length when returning 0, the caller needs to check that valid length is longer than or equals to bytes to read.
Timeline
ID reserved
By Linux
Published
- 13 months later
· 13 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.20% · top 90% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 6ac0aec6b0a651d64eef759fddf17d9145b51033 – < 5d53797ce7ce8fb1d95a5bebc5efa9418c4217a3
- affected 6ac0aec6b0a651d64eef759fddf17d9145b51033 – < 24cc679abbf31477d0cc6106ec83c2fbae6b3cdf
- affected 6ac0aec6b0a651d64eef759fddf17d9145b51033 – < fdd57c20d4408cac3c3c535c120d244e083406c9
- affected 6ac0aec6b0a651d64eef759fddf17d9145b51033 – < 6365569d62a75ddf53fb0c2936c16587a365984c
- affected 6ac0aec6b0a651d64eef759fddf17d9145b51033 – < b8ebf250997c5fb253582f42bfe98673801ebebd
- affected 5.3
- unaffected < 5.3
- unaffected 5.4.225 – ≤ 5.4.*
- unaffected 5.10.156 – ≤ 5.10.*
- unaffected 5.15.80 – ≤ 5.15.*
- unaffected 6.0.10 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (5)
- https://git.kernel.org/stable/c/5d53797ce7ce8fb1d95a5bebc5efa9418c4217a3 (opens in a new tab)
- https://git.kernel.org/stable/c/24cc679abbf31477d0cc6106ec83c2fbae6b3cdf (opens in a new tab)
- https://git.kernel.org/stable/c/fdd57c20d4408cac3c3c535c120d244e083406c9 (opens in a new tab)
- https://git.kernel.org/stable/c/6365569d62a75ddf53fb0c2936c16587a365984c (opens in a new tab)
- https://git.kernel.org/stable/c/b8ebf250997c5fb253582f42bfe98673801ebebd (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)
- 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://trackcve.app/cve/CVE-2022-49790)Record last updated .