All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Cohen <orcohen@paloaltonetworks.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	jslaby@suse.com, textshell@uchuujin.de,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	sam@ravnborg.org, mpatocka@redhat.com, ghalat@redhat.com,
	linux-kernel@vger.kernel.org, jwilk@jwilk.net,
	Nadav Markus <nmarkus@paloaltonetworks.com>,
	syzkaller@googlegroups.com
Subject: Re: Bug report - slab-out-of-bounds in vcs_scr_readw
Date: Mon, 4 Nov 2019 08:15:18 -0800	[thread overview]
Message-ID: <CAM6JnLdrzCPOYyfTdmriFo7cRaGM4p2OEPd_0MHa3_WemamffA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1911041648280.30289@knanqh.ubzr>

@gregkh@linuxfoundation.org @nico@fluxnic.net  - Thanks for the quick response.
@gregkh@linuxfoundation.org  - Regarding your question, I don't think
the 1 byte buffer is related to the problem. (  it's just was there in
the initial reproducer the fuzzer created, and I forgot to remove it
while reducing code from the reproducer ).
I think the problem is related to the huge size argument , which
influences  the initialization of "this_round".

On Mon, Nov 4, 2019 at 7:50 AM Nicolas Pitre <nico@fluxnic.net> wrote:
>
> On Mon, 4 Nov 2019, Greg KH wrote:
>
> > On Mon, Nov 04, 2019 at 04:39:55AM -0800, Or Cohen wrote:
> > > Hi,
> > > I discovered a OOB access bug using Syzkaller and decided to report it,
> > > as I could not find a similar report in syzkaller mailing list,
> > > syzkaller-bugs mailing list
> [...]
> >
> > I am at another conference at the moment and can't look at this much
> > now, will try to later this week...
>
> I'll looking into it now.
>
>
> Nicolas

  reply	other threads:[~2019-11-04 16:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM6JnLeEnvjjQPyLeh+8dt5wGNud_vks5k_eXJZy2T1H7ao=hQ@mail.gmail.com>
2019-11-04 15:24 ` Bug report - slab-out-of-bounds in vcs_scr_readw Greg KH
2019-11-04 15:50   ` Nicolas Pitre
2019-11-04 16:15     ` Or Cohen [this message]
2019-11-04 18:33       ` Nicolas Pitre
2019-11-05  6:54         ` Jiri Slaby
2019-11-05  9:03           ` Or Cohen
2019-11-05  9:14             ` Jiri Slaby
2019-11-05  9:33               ` Nicolas Pitre
2019-11-05 10:29                 ` Jiri Slaby
2019-11-05 10:53                   ` Dmitry Vyukov
2019-11-05 13:44                   ` Nicolas Pitre
2019-11-06 17:01                     ` Or Cohen
2019-11-26 21:55                 ` Nicolas Pitre
2019-11-27  6:45                   ` Greg KH
2019-11-27 16:24                     ` Nicolas Pitre
2019-11-27 16:30                       ` Greg KH

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=CAM6JnLdrzCPOYyfTdmriFo7cRaGM4p2OEPd_0MHa3_WemamffA@mail.gmail.com \
    --to=orcohen@paloaltonetworks.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=ghalat@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=jwilk@jwilk.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=nico@fluxnic.net \
    --cc=nmarkus@paloaltonetworks.com \
    --cc=sam@ravnborg.org \
    --cc=syzkaller@googlegroups.com \
    --cc=textshell@uchuujin.de \
    /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.