From: sashiko-bot@kernel.org
To: "Jiale Yao" <yaojiale02@163.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: (gigabyte_waterforce) reject short input reports
Date: Thu, 24 Sep 2026 15:20:16 +0000 [thread overview]
Message-ID: <20260924152016.D7AFD1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924151133.1233860-1-yaojiale02@163.com>
> The HID driver raw_event callback runs before HID core validates the
> received report length. waterforce_raw_event() reads the command bytes
> and then accesses fixed offsets for firmware or status data without any
> length checks. A truncated report can therefore cause out-of-bounds reads
> and update hwmon state with data beyond the received report.
>
> Require both command bytes before identifying a report, then check the
> minimum length needed by the firmware and status paths before accessing
> their payloads. Commit 47669bec44fe ("HID: asus: refactor the two
> workqueues and init sequence") added equivalent raw-event length
> validation to hid-asus.
>
> Fixes: 42ac68e3d4ba ("hwmon: Add driver for Gigabyte AORUS Waterforce AIO coolers")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jiale Yao <yaojiale02@163.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924151133.1233860-1-yaojiale02@163.com?part=1
next prev parent reply other threads:[~2026-09-24 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 15:11 [PATCH] hwmon: (gigabyte_waterforce) reject short input reports Jiale Yao
2026-09-24 15:20 ` sashiko-bot [this message]
2026-09-24 16:12 ` Guenter Roeck
2026-09-27 8:52 ` jiale yao
2026-09-24 16:14 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260924152016.D7AFD1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=yaojiale02@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.