HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.76, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections A report in 2019 by the syzbot fuzzer was found to be connected to two errors in the HID core associated with Resolution Multipliers. One of the errors was fixed by commit ea427a222d8b ("HID: core: Fix deadloop in hid_apply_multiplier."), but the other has not been fixed. This error arises because hid_apply_multipler() assumes that every Resolution Multiplier control is contained in a Logical Collection, i.e., there's no way the routine can ever set multiplier_collection to NULL. This is in spite of the fact that the function starts with a big comment saying: • "The Resolution Multiplier control must be contained in the same • Logical Collection as the control(s) to which it is to be applied. ... • If no Logical Collection is • defined, the Resolution Multiplier is associated with all • controls in the report." • HID Usage Table, v1.12, Section 4.3.1, p30 * • Thus, search from the current collection upwards until we find a • logical collection... The comment and the code overlook the possibility that none of the collections found may be a Logical Collection. The fix is to set the multiplier_collection pointer to NULL if the collection found isn't a Logical Collection.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in 3a002e4029230d9a6be89f869b2328b258612f5c; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in 05dd7d10675b540b8b7b31035c0a8abb6e6f3b88; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in a32ea3f982b389ea43a41ce77b6fb70d74006d9b; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in bebf542e8d7c44a18a95f306b1b5dc160c823506; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in ed3d3883476423f337aac0f22c521819b3f1e970; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in ebaeca33d32c8bdb705a8c88267737a456f354b1; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in a5498f1f864ea26f4c613c77f54409c776a95a90; From 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc · fixed in 64f2657b579343cf923aa933f08074e6258eb07b
- Linux Linux
5.0
- KernelLinux
From 5.0.0 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.129; From 6.2.0 · fixed in 6.6.76; From 6.7.0 · fixed in 6.12.13; From 6.13.0 · fixed in 6.13.2
References 8
git.kernel.org
- stable/c/3a002e4029230d9a6be89f869b2328b258612f5c
- stable/c/05dd7d10675b540b8b7b31035c0a8abb6e6f3b88
- stable/c/a32ea3f982b389ea43a41ce77b6fb70d74006d9b
- stable/c/bebf542e8d7c44a18a95f306b1b5dc160c823506
- stable/c/ed3d3883476423f337aac0f22c521819b3f1e970
- stable/c/ebaeca33d32c8bdb705a8c88267737a456f354b1
- stable/c/a5498f1f864ea26f4c613c77f54409c776a95a90
- stable/c/64f2657b579343cf923aa933f08074e6258eb07b