CVE-2024-57993: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check
In the Linux kernel, the following vulnerability has been resolved:
HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check
syzbot has found a type mismatch between a USB pipe and the transfer
endpoint, which is triggered by the hid-thrustmaster driver[1].
There is a number of similar, already fixed issues [2].
In this case as in others, implementing check for endpoint type fixes the issue.
[1] https://syzkaller.appspot.com/bug?extid=040e8b3db6a96908d470
[2] https://syzkaller.appspot.com/bug?extid=348331f63b034f89b622
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel issue in the Thrustmaster HID driver. A malformed or unexpected USB HID endpoint can trigger a driver warning because the code did not confirm the endpoint type before use. The public record does not provide CVSS, confirmed impact beyond the warning, or evidence of active exploitation.
Executive priority
Handle through normal kernel patch management unless the environment allows untrusted USB device access at scale. Prioritize shared workstations, kiosks, labs, and other endpoints where peripheral control is weaker.
Technical view
The vulnerable area is `hid-thrustmaster` in the Linux kernel. syzbot reported a type mismatch between a USB pipe and transfer endpoint during `thrustmaster_probe`. The kernel fix adds endpoint type validation, consistent with similar previously fixed USB HID issues. Impact details are limited in the provided sources.
Likely exposure
Most relevant exposure is Linux systems that load the Thrustmaster HID driver and accept locally attached or otherwise controllable USB HID devices. Servers without USB peripheral access are less likely to be exposed. Distribution kernels may vary, so confirm package backports with vendor advisories.
Exploitation context
The source bundle cites syzbot discovery and kernel stable fixes. It does not cite public exploitation, CISA KEV listing, exploit code, or a proven remote attack path. Treat this as a local or physical USB-adjacent kernel hardening issue unless vendor guidance says otherwise.
Researcher notes
Evidence is incomplete for impact severity: no CVSS, CWE, or exploitation claim is supplied. The strongest technical signal is the syzbot report and stable kernel commits adding endpoint type checks in `thrustmaster_probe`. Avoid assuming privilege escalation or remote compromise from the provided record alone.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check Debian LTS and your Linux vendor advisories for backported packages.
Restrict untrusted USB HID devices on managed endpoints.
Disable unnecessary HID or gaming peripheral support where operationally feasible.
Validation and detection
Identify Linux hosts that allow local USB peripheral attachment.
Check running kernel versions against vendor-fixed package versions.
Confirm the kernel includes the `hid-thrustmaster` endpoint validation fix.
Review fleet controls for blocking unauthorized USB HID devices.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-57993 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 02:07 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.