CVE-2025-38494: HID: core: do not bypass hid_hw_raw_request
In the Linux kernel, the following vulnerability has been resolved:
HID: core: do not bypass hid_hw_raw_request
hid_hw_raw_request() is actually useful to ensure the provided buffer
and length are valid. Directly calling in the low level transport driver
function bypassed those checks and allowed invalid paramto be used.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s HID handling bypassed checks intended to reject invalid buffer sizes and parameters. A locally authenticated attacker with limited privileges could potentially compromise confidentiality, integrity, or availability. The source bundle rates it 7.8 High, but does not establish active exploitation.
Executive priority
Treat this as a high-priority kernel update, especially on shared or multi-user Linux systems. It is not described as remotely exploitable, and active exploitation is unconfirmed. Schedule prompt remediation through normal kernel maintenance, accelerating systems that permit local access by untrusted users.
Technical view
Linux HID core code directly invoked a low-level transport function instead of hid_hw_raw_request(), bypassing buffer and length validation. The kernel stable fixes restore the validated request path. The supplied CVSS vector indicates local access, low complexity, low privileges, no user interaction, and potentially high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds where the vulnerable HID request path is present. The supplied version data is ambiguous and includes duplicated or unclear entries, so determine exposure using distribution advisories and confirmation that the applicable stable fix was backported.
Exploitation context
The CVSS assessment describes a local, low-privilege attack rather than a remotely reachable flaw. The bundle marks this CVE as absent from KEV and provides no evidence of exploitation in the wild, public exploit availability, or a demonstrated attack chain.
Researcher notes
The root issue is validation bypass at the HID core-to-transport boundary. Eight stable-tree fix references are supplied. Exact vulnerable-version interpretation is uncertain because the affected data contains duplicated hashes and unusual version entries, including “0”; verify commit ancestry or distribution backports rather than relying solely on version-string comparison.
Mitigation direction
Install a supported vendor kernel package containing the applicable Linux stable fix.
Reboot affected systems so the corrected kernel is actually running.
Consult distribution guidance where kernel versions use vendor-specific backports.
Prioritize multi-user systems where untrusted users can obtain local access.
Validation and detection
Inventory exact running kernel builds across Linux hosts.
Check vendor advisories for whether each build is affected or fixed.
Confirm the applicable stable commit or documented backport is present.
Verify systems booted into the updated kernel after maintenance.
Monitor vendor advisories for revised affected-version or exploitation information.
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-2025-38494 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.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.