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: <9aea1fae7574506ec2cd4f4f18d8cd07197e268f.camel@ibm.com>
Date: Mon, 28 Jul 2025 17:32:50 +0000
From: Viacheslav Dubeyko <Slava.Dubeyko@....com>
To: "huk23@...udan.edu.cn" <huk23@...udan.edu.cn>,
        "yang.chenzhi@...o.com"
	<yang.chenzhi@...o.com>
CC: "slava@...eyko.com" <slava@...eyko.com>,
        "frank.li@...o.com"
	<frank.li@...o.com>,
        "glaubitz@...sik.fu-berlin.de"
	<glaubitz@...sik.fu-berlin.de>,
        "baishuoran@...eu.edu.cn"
	<baishuoran@...eu.edu.cn>,
        "linux-fsdevel@...r.kernel.org"
	<linux-fsdevel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>,
        "jjtan24@...udan.edu.cn"
	<jjtan24@...udan.edu.cn>
Subject: Re:  KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x268/0x290

On Mon, 2025-07-28 at 15:40 +0800, Chenzhi Yang wrote:
> > Hi Slava,
> > Thank you for taking your time.
> 
> > We originally obtained this issue's syz and C reproducers using Syzkaller's repro tool (refer to the URL below). The issue was triggered when we ran the syz reproducer through Syzkaller.
> 
> > Url: https://github.com/google/syzkaller/blob/master/docs/reproducing_crashes.md  
> 
> > Syzkaller also provides syz-execprog to verify whether the C program can trigger the issue. We are currently in the process of verifying whether the C reproducer can reliably reproduce the issue. Please allow us some time to complete this verification.
> 
> > We'll follow up with you once we have more concrete results.
> 
> > Best regards,
> > Kun
> 
> Hi Kun,
> 
> Just wanted to follow up, how is the verification of the C reproducer going?
> If it does reliably reproduce the issue, could you also let us know under what
> scenario or environment it occurs?
> 

I already shared the patch [1] for this issue.

Thanks,
Slava.

[1]
https://lore.kernel.org/linux-fsdevel/20250703214804.244077-1-slava@dubeyko.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ