Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-57986HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 20 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

CVSS scores of CVE-2024-57986, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.32% · top 75% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < 3a002e4029230d9a6be89f869b2328b258612f5c
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < 05dd7d10675b540b8b7b31035c0a8abb6e6f3b88
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < a32ea3f982b389ea43a41ce77b6fb70d74006d9b
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < bebf542e8d7c44a18a95f306b1b5dc160c823506
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < ed3d3883476423f337aac0f22c521819b3f1e970
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < ebaeca33d32c8bdb705a8c88267737a456f354b1
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < a5498f1f864ea26f4c613c77f54409c776a95a90
    • affected 5a4abb36f312cf83206b1b7d1308ba47cba0b3cc – < 64f2657b579343cf923aa933f08074e6258eb07b
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.4.291 – ≤ 5.4.*
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.76 – ≤ 6.6.*
    • unaffected 6.12.13 – ≤ 6.12.*
    • unaffected 6.13.2 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References12

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-57986 badge
[![CVE-2024-57986](https://cveledger.app/badge/CVE-2024-57986.svg)](https://cveledger.app/cve/CVE-2024-57986)

Record last updated .