From: Red Hat Product Security <secalert@redhat.com>
To: catalin.marinas@arm.com, syzkaller@googlegroups.com,
liujf628995@126.com, gregkh@linuxfoundation.org,
security@kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Re: use-after-free in kmemleak_scan？
Date: Thu, 29 Jun 2023 02:27:04 -0700 (PDT) [thread overview]
Message-ID: <684922.16309.1688030824237@app133038.ytz3.service-now.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1624 bytes --]
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" <gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]> 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
[-- Attachment #1.2: Type: text/html, Size: 2597 bytes --]
reply other threads:[~2023-06-29 9:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=684922.16309.1688030824237@app133038.ytz3.service-now.com \
--to=secalert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liujf628995@126.com \
--cc=security@kernel.org \
--cc=syzkaller@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox