linux-kernel - Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in __mmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <hfvevenewnofccufdpvrbridrqrpsfe7wspj5s6bng6bphddqi@hopyq3cuqfs2>
Date: Tue, 24 Dec 2024 11:35:23 -0500
From: "Liam R. Howlett" <Liam.Howlett@...cle.com>
To: Kun Hu <huk23@...udan.edu.cn>
Cc: akpm@...ux-foundation.org, lorenzo.stoakes@...cle.com, vbabka@...e.cz,
        jannh@...gle.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        "jjtan24@...udan.edu.cn" <jjtan24@...udan.edu.cn>
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in __mmap_region

* Kun Hu <huk23@...udan.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/