linux-kernel - Re: KASAN: vmalloc-out-of-bounds Read in copy_from

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 for Android: free password hash cracker in your pocket

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

Message-ID: <73f0635b-b47c-40a7-b63c-b2a4fa0d881a@intel.com>
Date: Mon, 21 Jul 2025 10:32:56 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: 白烁冉 <baishuoran@...eu.edu.cn>,
 Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>
Cc: Kun Hu <huk23@...udan.edu.cn>, Jiaji Qin <jjtan24@...udan.edu.cn>,
 x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
 linux-kernel@...r.kernel.org
Subject: Re: KASAN: vmalloc-out-of-bounds Read in copy_from_buffer

On 7/18/25 02:40, 白烁冉 wrote:
> When using our customized Syzkaller to fuzz the latest Linux kernel,
> the following crash was triggered.

This looks like it can only be triggered with privileges. I'd certainly
take a patch to fix it, but it seems like something that is very
unlikely to be an issue in practice, so not a super high priority.

If you could actually narrow down precisely what overflowed or where the
code went wrong, I might take a closer look.