CVE-2024-57986 is an input-validation flaw in the Linux kernel HID core's hid_apply_multiplier() handling of HID Resolution Multiplier controls. The function assumed that a Resolution Multiplier would be contained in a Logical Collection, although the HID specification permits a multiplier without a Logical Collection to apply to all controls in the report. When no applicable Logical Collection exists, the code could retain a non-NULL multiplier_collection pointer instead of setting it to NULL. The issue affects drivers/hid/hid-core.c and was introduced in Linux kernel 5.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel HID resolution-multiplier collection validation flaw.
Linux kernel HID core input-validation flaw.
A Linux kernel HID core flaw in Resolution Multiplier handling, where hid_apply_multiplier() incorrectly assumes a Logical Collection exists, contrary to HID specification behavior for controls with no Logical Collection.
An improper-input-validation vulnerability in the Linux kernel HID core affecting Resolution Multiplier handling. A malformed HID report descriptor without a Logical Collection can trigger the flawed assumption, with availability impact assessed as high (e.g., denial of service).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.