From: Greg KH <gregkh@linuxfoundation.org>
To: 慕冬亮 <mudongliangabcd@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, shuah@kernel.org,
valentina.manea.m@gmail.com, hdanton@sina.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: “KASAN: null-ptr-deref Write in event_handler” and "KASAN: null-ptr-deref Write in vhci_shutdown_connection" should share the same root cause.
Date: Wed, 20 Jan 2021 08:54:27 +0100 [thread overview]
Message-ID: <YAfhs++HLaTsejb2@kroah.com> (raw)
In-Reply-To: <CAD-N9QUVDpHjSwZa+w3Zxx_Pn5ZrBKuhGhbg9PoyR=xbrMb88g@mail.gmail.com>
On Wed, Jan 20, 2021 at 11:22:11AM +0800, 慕冬亮 wrote:
> Dear kernel developers,
>
> I found that on the syzbot dashboard, “KASAN: null-ptr-deref Write in
> event_handler”[1] and
> "KASAN: null-ptr-deref Write in vhci_shutdown_connection" () should
> share the same root cause.
>
>
> The reasons for the above statement:
> 1) the stack trace is the same, and this title difference is due to
> the inline property of "vhci_shutdown_connection";
> 2) their PoCs are the same as each other.
>
> If you can have any issues with this statement or our information is
> useful to you, please let us know. Thanks very much.
>
> [1] KASAN: null-ptr-deref Write in event_handler -
> https://syzkaller.appspot.com/bug?id=28cccdd18b4bb8670d077937fb8d4849dca96230
> [2] KASAN: null-ptr-deref Write in vhci_shutdown_connection -
> https://syzkaller.appspot.com/bug?id=c21c07f3d51769405e8efc027bdb927515dcc7d6
Great, care to create a patch for this problem? That's the best way to
solve these things.
thanks,
greg k-h
prev parent reply other threads:[~2021-01-20 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 3:22 “KASAN: null-ptr-deref Write in event_handler” and "KASAN: null-ptr-deref Write in vhci_shutdown_connection" should share the same root cause 慕冬亮
2021-01-20 7:54 ` Greg KH [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=YAfhs++HLaTsejb2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=shuah@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=valentina.manea.m@gmail.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 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.