From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Kun Hu <huk23@m.fudan.edu.cn>
Cc: akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
vbabka@suse.cz, jannh@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"jjtan24@m.fudan.edu.cn" <jjtan24@m.fudan.edu.cn>
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in __mmap_region
Date: Tue, 24 Dec 2024 11:35:23 -0500 [thread overview]
Message-ID: <hfvevenewnofccufdpvrbridrqrpsfe7wspj5s6bng6bphddqi@hopyq3cuqfs2> (raw)
In-Reply-To: <29B3EC03-A27C-4BC6-A8C5-F7A4497D8CED@m.fudan.edu.cn>
* Kun Hu <huk23@m.fudan.edu.cn> [241224 07:13]:
> Hello,
>
> When using fuzzer tool to fuzz the latest Linux kernel, the following crash
> was triggered.
>
> HEAD commit: 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8
> git tree: upstream
> Console output: https://drive.google.com/file/d/1_GxT_B3JkCE8Q6r6PGgG27uNn5cgzZm3/view?usp=sharing
> Kernel config: https://drive.google.com/file/d/1RhT5dFTs6Vx1U71PbpenN7TPtnPoa3NI/view?usp=sharing
> C reproducer: https://drive.google.com/file/d/1zyZSM-hp1UInnE-AA9J3NXmMCV7DCqgf/view?usp=sharing
> Syzlang reproducer: https://drive.google.com/file/d/1W0yvbKYi6GaAaG0YNeDVacN3eEa8rxot/view?usp=sharing
>
> We are triggering the same issue and I hope this information is useful to you. If you fix this issue, please let me know.
The fix is on its way upstream. [1]
It is on the dashboard page of the syzbot report you are responding
to...
It specifies the closes and reported-by in the commit.
Are you saying it happens with this fix or did you not test the fix?
Thanks,
Liam
[1] https://lore.kernel.org/all/20241206215229.244413-1-lorenzo.stoakes@oracle.com/T/
next prev parent reply other threads:[~2024-12-24 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 12:13 Kun Hu
2024-12-24 16:35 ` Liam R. Howlett [this message]
2025-01-16 19:28 ` Liam R. Howlett
2025-01-17 2:13 ` Fudam
-- strict thread matches above, loose matches on Subject: below --
2024-12-06 21:18 syzbot
2024-12-06 21:29 ` Jann Horn
2024-12-06 21:36 ` Lorenzo Stoakes
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=hfvevenewnofccufdpvrbridrqrpsfe7wspj5s6bng6bphddqi@hopyq3cuqfs2 \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=huk23@m.fudan.edu.cn \
--cc=jannh@google.com \
--cc=jjtan24@m.fudan.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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