CVE-2024-57986

HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections

State
Published
Severity
7.1 High
Published
Feb 27, 2025
Updated
Oct 15, 2026
Reserved
Feb 27, 2025

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.17.1 HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before 3a002e4029230d9a6be89f869b2328b258612f5cAffected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before 05dd7d10675b540b8b7b31035c0a8abb6e6f3b88Affected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before a32ea3f982b389ea43a41ce77b6fb70d74006d9bAffected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before bebf542e8d7c44a18a95f306b1b5dc160c823506Affected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before ed3d3883476423f337aac0f22c521819b3f1e970Affected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before ebaeca33d32c8bdb705a8c88267737a456f354b1Affected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before a5498f1f864ea26f4c613c77f54409c776a95a90Affected
  • 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc to before 64f2657b579343cf923aa933f08074e6258eb07bAffected
LinuxLinux
  • 5.0Affected
  • before 5.0Not affected
  • 5.4.291 through 5.4.*Not affected
  • 5.10.235 through 5.10.*Not affected
  • 5.15.179 through 5.15.*Not affected
  • 6.1.129 through 6.1.*Not affected
  • 6.6.76 through 6.6.*Not affected
  • 6.12.13 through 6.12.*Not affected
  • 6.13.2 through 6.13.*Not affected
  • 6.14 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.