CVE-2026-99721

Description

A flaw was found in the Linux kernel's aquacomputer_d5next hardware monitoring driver. An attacker capable of connecting a crafted Human Interface Device (HID) or sending truncated status reports can trigger an out-of-bounds memory read because the driver accesses status fields before validating the report buffer length. This vulnerability may allow an attacker to cause a Denial of Service (DoS) via a system crash or corrupt hardware monitoring data.

Statement

This vulnerability is rated as Moderate impact because exploitation requires physical access to attach a malicious USB device to the host, though virtualized environments with guest USB pass-through could also expose the driver interface. Specialized Aqua Computer liquid-cooling hardware is rarely deployed in standard Red Hat Enterprise Linux enterprise environments, significantly limiting exposure in typical production setups. Successful exploitation triggers an out-of-bounds read condition that can crash the kernel, resulting in a denial of service.

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.