CVE-2026-80604

HID: core: Fix OOB read in hid_get_report for numbered reports

HIGH
8.8
CVSS Score
Published: August 28, 2026 at 06:48 AM UTC
Updated: October 16, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: HID: core: Fix OOB read in hid_get_report for numbered reports When a caller passes a size of 0 to hid_report_raw_event() for a numbered report, the function originally called hid_get_report() before performing any size validation. Inside hid_get_report(), if the report is numbered (report_enum->numbered is true), it unconditionally dereferences data[0] to extract the report ID. With a size of 0, this results in an out-of-bounds read or kernel panic. Fix this by moving the numbered report size validation check before the call to hid_get_report(), ensuring that size is at least 1 before dereferencing the data pointer.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

121dc93ae1fcaa4b9a601eca6b3ca2e969c2fe2f2c85c61d1332e1e16f020d76951baf167dcb6f7a5.10.2595.15.210509c2605065004fc4cd86ee50a9350d40278530759bfdb41a34cf5d6af1c637348714c2b5a6ca6766.1.1766.12.936.18.336.6.1437.0.107.1710a946b1aa2c35dc56f86621f436938f31ba1a59e36568e67f817c728f9d79049d212da79109a75a4d6cb7cf45bddc76c78ed5fd683328af9e2018ffb3f7ec2606cdc7c6ef30970f381e571866bfd54
Vendor states this is fixed in 30ff978af92cb51c9ba99f96fc4f4ac80d7001ba (fixed)
Vendor states this is fixed in af1a9b65ebe8a948eda805c14b78d4d0767cb1b5 (fixed)
Vendor states this is fixed in c1fc0d3aff26ec9ff885b3e4c92eba98cf349678 (fixed)
Vendor states this is fixed in c39f5765ad840b71ff8db812d0210f216cca96e4 (fixed)
Vendor states this is fixed in c973d53bcd420b58c4a34c68198746286d77e9fa (fixed)
Vendor states this is fixed in dd395744e4ed87956fcbf81ecc6a20c51e35fa4e (fixed)
Vendor states this is fixed in f7e8117e42b20c30d2a5edab82c944a5e381d791 (fixed)
Vendor states this is fixed in f8896b684e246f3f00f45ba2b6803ae59b9cc768 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card