Hello! INC2660272 (Re: use-after-free in kmemleak_scan？) has been updated. Opened for: gregkh@linuxfoundation.org Followers: liujf628995@126.com, security@kernel.org, catalin.marinas@arm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller@googlegroups.com, akpm@linux-foundation.org A Guest updated your request with the following comments: Reply from: liujf628995@126.com [mailto:liujf628995@126.com]  ok,I will send the mail by plain/text again by another email address,this crash occured many times in my fuzzing,but I'm sorry that I have not a reproducer or a patch. At 2023-06-29 13:56:57, "Greg KH" wrote: >On Thu, Jun 29, 2023 at 11:19:36AM +0800, liujf628995 wrote: >> hello,here is a crash from syzkaller,it looks like happened in kmemleak scan.It [http://scan.It] could not be reproduced by syzkaller because this should not have been caused by syscall fuzz.I don't know what rhe reason for this，please check it.My [http://it.My] fuzzed linux kernel is linux-6.2（commit/c9c3395d5e3dcc6daee66c6908354d47bf98cb0c） > >If you have a reproducer or a patch, we will be glad to review it, >otherwise just sending syzbot reports like this (especially in html >format which is rejected by the mailing lists), will not go very far as >we have loads of them already. > >thanks, > >greg k-h How can I track and update my request? To respond, reply to this email. You may also create a new email and include the request number (INC2660272) in the subject. Thank you, Product Security Ref:MSG76176793