Kernel memory corruption via undersized HID report buffer
Published Jul 28, 2025 · Updated Aug 5, 2026
Out-of-bounds memory access in the Linux kernel HID core allows adjacent attackers to corrupt kernel memory via crafted HID reports. hid_alloc_report_buf allocates seven padding bytes but omits the extra report-ID byte required when report->id is zero, leaving transport operations one byte beyond the allocation. An unauthenticated malicious or spoofed Bluetooth HID peripheral reaches the path during automatic enumeration and can disclose or corrupt adjacent kernel heap data or crash the host.
Summary
What happened
Out-of-bounds memory access in the Linux kernel HID core allows adjacent attackers to corrupt kernel memory via crafted HID reports. hid_alloc_report_buf allocates seven padding bytes but omits the extra report-ID byte required when report->id is zero, leaving transport operations one byte beyond the allocation. An unauthenticated malicious or spoofed Bluetooth HID peripheral reaches the path during automatic enumeration and can disclose or corrupt adjacent kernel heap data or crash the host.
The record
- CVE
- CVE-2025-38495
- Published
- Jul 28, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1200
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.15
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <4f15ee98304b96e164ff2340e1dfd6181c3f42aa
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <7228e36c7875e4b035374cf68ca5e44dffa596b2
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <7fa83d0043370003e9a0b46ab7ae8f53b00fab06
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <9f2892f7233a8f1320fe671d0f95f122191bfbcd
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <a262370f385e53ff7470efdcdaf40468e5756717
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <a47d9d9895bad9ce0e840a39836f19ca0b2a343a
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <d3ed1d84a84538a39b3eb2055d6a97a936c108f2
- Affected versionversion=4fa5a7f76cc7b6ac87f57741edd2b124851d119f <fcda39a9c5b834346088c14b1374336b079466c1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo