Linux Kernel up to 7.1.4 HID Core hid_report_raw_event size out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.32+

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.4 and classified as problematic. Affected by this issue is the function hid_report_raw_event of the component HID Core. The manipulation of the argument size results in out-of-bounds. This vulnerability is known as CVE-2026-80604. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 7.1.4. Affected is the function hid_report_raw_event of the component HID Core. The manipulation of the argument size with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-80604 since 08/26/2026. The exploitability is told to be easy. The attack needs to be approached locally. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40 or 7.1.5 eliminates this vulnerability. Applying the patch f8896b684e246f3f00f45ba2b6803ae59b9cc768/30ff978af92cb51c9ba99f96fc4f4ac80d7001ba/c39f5765ad840b71ff8db812d0210f216cca96e4/c973d53bcd420b58c4a34c68198746286d77e9fa/c1fc0d3aff26ec9ff885b3e4c92eba98cf349678/dd395744e4ed87956fcbf81ecc6a20c51e35fa4e/f7e8117e42b20c30d2a5edab82c944a5e381d791/af1a9b65ebe8a948eda805c14b78d4d0767cb1b5 is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5
Patch: f8896b684e246f3f00f45ba2b6803ae59b9cc768/30ff978af92cb51c9ba99f96fc4f4ac80d7001ba/c39f5765ad840b71ff8db812d0210f216cca96e4/c973d53bcd420b58c4a34c68198746286d77e9fa/c1fc0d3aff26ec9ff885b3e4c92eba98cf349678/dd395744e4ed87956fcbf81ecc6a20c51e35fa4e/f7e8117e42b20c30d2a5edab82c944a5e381d791/af1a9b65ebe8a948eda805c14b78d4d0767cb1b5

Timelineinfo

08/26/2026 CVE reserved
08/28/2026 +2 days Advisory disclosed
08/28/2026 +0 days VulDB entry created
08/28/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80604 (🔒)
GCVE (CVE): GCVE-0-2026-80604
GCVE (VulDB): GCVE-100-396540

Entryinfo

Created: 08/28/2026 10:03
Changes: 08/28/2026 10:03 (60)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!