CVE-2026-99327

Description

A flaw was found in the Linux kernel's Roccat Kova[+] mouse Human Interface Device (HID) driver. The driver processes incoming raw events without verifying that the received data buffer is large enough to contain a complete button report structure. An attacker capable of connecting a crafted USB device can send truncated reports to trigger an out-of-bounds read. This flaw may allow an attacker to cause a denial of service through a kernel crash or potentially disclose sensitive kernel memory.

Statement

This vulnerability is rated as Moderate impact because successful exploitation requires physical access to attach a malicious USB device, or the ability to attach an emulated USB device in a virtualized guest environment, limiting the overall attack surface. Under typical enterprise deployments, standard server and workstation configurations do not employ Roccat gaming peripherals, significantly reducing real-world exposure. When triggered by malformed HID reports, the flaw results in a kernel crash causing a denial of service, without impacting confidentiality or data integrity.

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 Score4.6N/AN/A
Attack VectorPhysicalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.