* “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 3:22 慕冬亮
2021-01-20 7:54 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: 慕冬亮 @ 2021-01-20 3:22 UTC (permalink / raw)
To: Greg KH, linux-kernel, linux-usb, shuah, valentina.manea.m,
hdanton, syzkaller-bugs, syzkaller
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
--
My best regards to you.
No System Is Safe!
Dongliang Mu
^ permalink raw reply [flat|nested] 2+ messages in thread
* 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.
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
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2021-01-20 7:54 UTC (permalink / raw)
To: 慕冬亮
Cc: linux-kernel, linux-usb, shuah, valentina.manea.m, hdanton,
syzkaller-bugs, syzkaller
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-01-20 7:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox