From: Benjamin Tissoires <bentiss@kernel.org>
To: dan.carpenter@linaro.org, Andrew Ballance <andrewjballance@gmail.com>
Cc: jikos@kernel.org, linux-input@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
luke@ljones.dev, skhan@linuxfoundation.org,
syzbot+07762f019fd03d01f04c@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com,
Benjamin Tissoires <bentiss@kernel.org>,
Jiri Kosina <jikos@kernel.org>
Subject: Re: [PATCH v2] hid: asus: asus_report_fixup: fix potential read out of bounds
Date: Thu, 06 Jun 2024 10:31:03 +0200 [thread overview]
Message-ID: <171766266391.2918443.4596267274284818390.b4-ty@kernel.org> (raw)
In-Reply-To: <20240602085023.1720492-1-andrewjballance@gmail.com>
On Sun, 02 Jun 2024 03:50:23 -0500, Andrew Ballance wrote:
> syzbot reported a potential read out of bounds in asus_report_fixup.
>
> this patch adds checks so that a read out of bounds will not occur
>
>
Applied to hid/hid.git (for-6.10/upstream-fixes), thanks!
[1/1] hid: asus: asus_report_fixup: fix potential read out of bounds
https://git.kernel.org/hid/hid/c/cfacaaf33cd7
Cheers,
--
Benjamin Tissoires <bentiss@kernel.org>
prev parent reply other threads:[~2024-06-06 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000915d550619389e8a@google.com>
2024-05-28 5:05 ` [PATCH] hid: asus: asus_report_fixup: fix potential read out of bounds Andrew Ballance
2024-05-28 5:46 ` [syzbot] [input?] [usb?] KMSAN: uninit-value in asus_report_fixup syzbot
2024-05-31 8:59 ` [PATCH] hid: asus: asus_report_fixup: fix potential read out of bounds Dan Carpenter
2024-06-02 8:50 ` [PATCH v2] " Andrew Ballance
2024-06-02 10:57 ` Greg KH
2024-06-06 8:31 ` Benjamin Tissoires [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=171766266391.2918443.4596267274284818390.b4-ty@kernel.org \
--to=bentiss@kernel.org \
--cc=andrewjballance@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+07762f019fd03d01f04c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox