[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YAfhs++HLaTsejb2@kroah.com>
Date: Wed, 20 Jan 2021 08:54:27 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: 慕冬亮 <mudongliangabcd@...il.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
linux-usb@...r.kernel.org, shuah@...nel.org,
valentina.manea.m@...il.com, hdanton@...a.com,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
syzkaller <syzkaller@...glegroups.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.
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
Powered by blists - more mailing lists