From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: bakabaka9 <baka9@bakabaka9.tech>,
jikos@kernel.org, jic23@kernel.org, bentiss@kernel.org
Cc: linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH v2 RESEND] HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature
Date: Tue, 11 Aug 2026 15:24:16 -0700 [thread overview]
Message-ID: <45d002c27ec333bec9bc83b7d164444d6a0b510c.camel@linux.intel.com> (raw)
In-Reply-To: <20260805185753.3069-1-baka9@bakabaka9.tech>
On Wed, 2026-08-05 at 18:57 +0000, bakabaka9 wrote:
> From: Xingrui Li <baka9@bakabaka9.tech>
>
> sensor_hub_get_feature() clamps its return value to the caller's
> buffer
> size, but the copy loop still copies field->report_size / 8 bytes for
> each report value. A malicious HID descriptor can advertise a large
> feature field size while an IIO caller supplies a small stack buffer,
> such as a single s32, causing an out-of-bounds write.
>
> HID core stores parsed report values in __s32 slots and clamps
> extracted
> values to 32 bits. Reject feature fields that require more than one
> slot
> per value, guard the total byte count calculation, and clamp each
> per-value copy to the remaining caller buffer.
>
> Fixes: 5459ada2b3cd69 ("HID: sensor-hub: Fix packing of result buffer
> for feature report")
> Cc: stable@kernel.org
> Assisted-by: OpenAI:GPT-5.5-Cyber
> Signed-off-by: Xingrui Li <baka9@bakabaka9.tech>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/hid/hid-sensor-hub.c | 42 +++++++++++++++++++++-------------
> --
> 1 file changed, 25 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/hid/hid-sensor-hub.c b/drivers/hid/hid-sensor-
> hub.c
> index 34f710c465b8..6470a290ebfc 100644
> --- a/drivers/hid/hid-sensor-hub.c
> +++ b/drivers/hid/hid-sensor-hub.c
> @@ -239,12 +239,17 @@ int sensor_hub_get_feature(struct
> hid_sensor_hub_device *hsdev, u32 report_id,
> u32 field_index, int buffer_size, void
> *buffer)
> {
> struct hid_report *report;
> + struct hid_field *field;
> struct sensor_hub_data *data = hid_get_drvdata(hsdev->hdev);
> - int report_size;
> + size_t field_size;
> + size_t report_size;
> + size_t copied = 0;
> + size_t to_copy;
> int ret = 0;
> - u8 *val_ptr;
> - int buffer_index = 0;
> - int i;
> + unsigned int i;
> +
> + if (!buffer || buffer_size <= 0)
> + return -EINVAL;
>
> memset(buffer, 0, buffer_size);
>
> @@ -258,26 +263,29 @@ int sensor_hub_get_feature(struct
> hid_sensor_hub_device *hsdev, u32 report_id,
> hid_hw_request(hsdev->hdev, report, HID_REQ_GET_REPORT);
> hid_hw_wait(hsdev->hdev);
>
> + field = report->field[field_index];
> +
> /* calculate number of bytes required to read this field */
> - report_size = DIV_ROUND_UP(report->field[field_index]-
> >report_size,
> - 8) *
> - report->field[field_index]-
> >report_count;
> - if (!report_size) {
> + field_size = DIV_ROUND_UP(field->report_size, 8);
> + /* HID core stores each parsed report value in a __s32 slot.
> */
> + if (!field_size || field_size > sizeof(field->value[0])) {
> + ret = -EINVAL;
> + goto done_proc;
> + }
> + if (field->report_count > SIZE_MAX / field_size) {
> ret = -EINVAL;
> goto done_proc;
> }
> - ret = min(report_size, buffer_size);
>
> - val_ptr = (u8 *)report->field[field_index]->value;
> - for (i = 0; i < report->field[field_index]->report_count;
> ++i) {
> - if (buffer_index >= ret)
> - break;
> + report_size = field_size * field->report_count;
> + report_size = min_t(size_t, report_size, buffer_size);
>
> - memcpy(&((u8 *)buffer)[buffer_index], val_ptr,
> - report->field[field_index]->report_size / 8);
> - val_ptr += sizeof(__s32);
> - buffer_index += (report->field[field_index]-
> >report_size / 8);
> + for (i = 0; i < field->report_count && copied < report_size;
> ++i) {
> + to_copy = min(field_size, report_size - copied);
> + memcpy(&((u8 *)buffer)[copied], &field->value[i],
> to_copy);
> + copied += to_copy;
> }
> + ret = copied;
>
> done_proc:
> mutex_unlock(&data->mutex);
prev parent reply other threads:[~2026-08-11 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 18:57 [PATCH v2 RESEND] HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature bakabaka9
2026-08-05 20:11 ` sashiko-bot
2026-08-11 22:24 ` srinivas pandruvada [this message]
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=45d002c27ec333bec9bc83b7d164444d6a0b510c.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=baka9@bakabaka9.tech \
--cc=bentiss@kernel.org \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=stable@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox