CVE-2026-80604

Description

A flaw was found in the Linux kernel's Human Interface Device (HID) core. When processing numbered reports, the hid_get_report() function can attempt to read data from an invalid memory location if a size of zero is provided. This out-of-bounds read can lead to a kernel panic, effectively causing a denial of service for the system.

Statement

A numbered HID report can reach hid_get_report with size 0 before input length validation, causing an out of bounds read of data(0) while extracting the report ID. A malicious or faulty HID device can trigger this through the HID input path and may cause a kernel crash or warning depending on memory layout and transport behavior. For the CVSS the PR:N because the attacker does not need privileges on the target once the malicious HID input can be delivered. The base vector treats this mainly as a physical device attack with user involvement for device connection or pairing. The paranoid vector treats wireless or already connected HID transports as adjacent and uses C:L because this is an OOB read, while integrity remains N because no write primitive is shown. Impact is mainly denial of service via kernel crash.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.1N/A8.8
Attack VectorAdjacent NetworkN/AAdjacent Network
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.

Confidentiality

Technical Impact: Read Memory; Read Files or Directories

An attacker could read confidential data if they are able to control resource references.

Integrity,Confidentiality,Availability

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.