linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+a9fefd18c7b240f19c54@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	rafael@kernel.org, stern@rowland.harvard.edu,
	syzkaller-bugs@googlegroups.com
Subject: KASAN: slab-out-of-bounds Read in hex_string
Date: Mon, 29 Apr 2019 13:52:01 -0700	[thread overview]
Message-ID: <000000000000bc95620587b1748e@google.com> (raw)

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger  
crash:

Reported-and-tested-by:  
syzbot+a9fefd18c7b240f19c54@syzkaller.appspotmail.com

Tested on:

commit:         43151d6c usb-fuzzer: main usb gadget fuzzer driver
git tree:       https://github.com/google/kasan.git usb-fuzzer
kernel config:  https://syzkaller.appspot.com/x/.config?x=4183eeef650d1234
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16c59788a00000

Note: testing is done by a robot and is best-effort only.

WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+a9fefd18c7b240f19c54@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	rafael@kernel.org, stern@rowland.harvard.edu,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in hex_string
Date: Mon, 29 Apr 2019 13:52:01 -0700	[thread overview]
Message-ID: <000000000000bc95620587b1748e@google.com> (raw)
Message-ID: <20190429205201.7cMyNqjAfW3mGFKA1mfT0jgY0sCfPGeacnk0xqvwDBk@z> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1904291604510.1632-100000@iolanthe.rowland.org>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger  
crash:

Reported-and-tested-by:  
syzbot+a9fefd18c7b240f19c54@syzkaller.appspotmail.com

Tested on:

commit:         43151d6c usb-fuzzer: main usb gadget fuzzer driver
git tree:       https://github.com/google/kasan.git usb-fuzzer
kernel config:  https://syzkaller.appspot.com/x/.config?x=4183eeef650d1234
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16c59788a00000

Note: testing is done by a robot and is best-effort only.

         reply	other threads:[~2019-04-29 20:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29 12:06 KASAN: slab-out-of-bounds Read in hex_string syzbot
2019-04-29 20:07 ` Alan Stern
2019-04-29 20:07   ` Alan Stern
2019-04-29 20:24   ` Andrey Konovalov
2019-04-29 20:24     ` Andrey Konovalov
2019-04-29 20:52   ` syzbot [this message]
2019-04-29 20:52     ` syzbot
2019-04-29 21:09   ` Eric Biggers
2019-04-29 21:09     ` Eric Biggers
2019-04-30 14:13     ` Alan Stern
2019-04-30 14:13       ` Alan Stern
2019-08-13 12:55       ` Andrey Konovalov
2020-03-18 15:46 ` Andrey Konovalov

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=000000000000bc95620587b1748e@google.com \
    --to=syzbot+a9fefd18c7b240f19c54@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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;
as well as URLs for NNTP newsgroup(s).