Skip to content
statance
MenuClose
unknown

CVE-2026-97538

hwmon: (asus_rog_ryujin) Validate HID report lengths

Published 25 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-19 15:06 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

hwmon: (asus_rog_ryujin) Validate HID report lengths

rog_ryujin_raw_event() parses response headers and payload fields without first checking that they are present in the received report. A short report can therefore make the driver consume uninitialized bytes from the HID transport buffer and expose them as sensor values through sysfs.

Validate the response header and the fields used by each response type before parsing them.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: ed3e03790c5c9f29f032dde9bb784e198984a759 to < 995f22b2881835b518b3f99240d00781c9df0235; affected: ed3e03790c5c9f29f032dde9bb784e198984a759 to < 49cc6d5c00a7f75540d1a4324e01be4067ee652c; affected: ed3e03790c5c9f29f032dde9bb784e198984a759 to < 1caa5f9399ff107a8fa221b1eaca0a9e729d3758; affected: ed3e03790c5c9f29f032dde9bb784e198984a759 to < 8042312e73c50de82634ce63eae7cf219464b481See vendor advisory
LinuxLinuxaffected: 6.9; unaffected: 0 to < 6.9; unaffected: 6.12.114 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.7 to ≤ 7.2.*; unaffected: 7.3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed