CVE-2026-99721: hwmon: (aquacomputer_d5next) reject short status reports
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (aquacomputerd5next) reject short status reports
The HID rawevent callback runs before HID core validates the received report length. aqcrawevent() reads device-specific status fields at fixed offsets, including multi-byte values, without first ensuring that the received buffer contains every field. A truncated report can therefore cause out-of-bounds reads and update hwmon state with unrelated data.
The required length differs between supported devices and cannot be derived from the HID report descriptor. Define the minimum length needed by each asynchronous status format, select it while configuring the device, and reject reports that do not contain the last field accessed by that format. Keep the published length zero until probe configuration is complete, which also excludes legacy devices whose status is retrieved through feature reports.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1 - Compensating control
During probe configuration, determine the minimum report length for each asynchronous status format and keep the published length at zero until configuration is complete. Reject status reports that do not contain the last field accessed by that format.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel aquacomputer_d5next hwmon driver are exposed when handling asynchronous HID status reports from supported devices. Legacy devices whose status is obtained through feature reports are excluded by the described length-gating behavior.
What would an attacker need to exploit this?
An attacker would need to cause the driver to receive a truncated HID status report. The vulnerable callback processes reports before HID core validates their length, allowing fixed-offset field reads beyond the received buffer.
What is the impact of a short report?
A truncated report can cause out-of-bounds reads and may update hardware-monitoring state with unrelated data.
How does the fix mitigate the issue?
The fix assigns a device-specific minimum length for each asynchronous status format and rejects reports that do not include the last field the driver accesses. The required length is selected during device configuration and remains zero until probe configuration is complete.