linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Anirudh Rayabharam <mail@anirudhrb.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel-mentees@lists.linuxfoundation.org,
	syzbot+7c2bb71996f95a82524c@syzkaller.appspotmail.com,
	Linux USB Mailing List <linux-usb@vger.kernel.org>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usbhid: fix info leak in hid_submit_ctrl
Date: Wed, 5 May 2021 15:28:31 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2105051528090.28378@cbobk.fhfr.pm> (raw)
In-Reply-To: <CAO-hwJJ4u5NZ-81Tq3PGu-F9r3iUSCiKp=JUsTfuVsyd-Sxsew@mail.gmail.com>

On Wed, 5 May 2021, Benjamin Tissoires wrote:

> I don't have a reproducer like syzbot has for the exact bug here, as I 
> am relying on one real USB device to check if usbhid is not too broken. 
> However, the test suite should catch if there is an error implied by the 
> hid_report_len() change.

Yes, that was exactly what I wanted to check, sorry for not being verbose 
enough :)

> Anyway, I manually started the job and will report when it is done.

Thanks,

-- 
Jiri Kosina
SUSE Labs


  reply	other threads:[~2021-05-05 13:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 17:33 [PATCH] usbhid: fix info leak in hid_submit_ctrl Anirudh Rayabharam
2021-05-05 12:42 ` Jiri Kosina
2021-05-05 13:25   ` Benjamin Tissoires
2021-05-05 13:28     ` Jiri Kosina [this message]
2021-05-05 13:47       ` Benjamin Tissoires
2021-05-05 13:52         ` Jiri Kosina

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=nycvar.YFH.7.76.2105051528090.28378@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=gregkh@linuxfoundation.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=mail@anirudhrb.com \
    --cc=syzbot+7c2bb71996f95a82524c@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).