linux-kernel - Re: Lion, can you take a look at his? WAS(Re: [syzbot] [net?] general protection fault in htb_qlen

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAM0EoM=TwzOF9Osb4qtHzxdBcHewKFq_nAYAqx64UTjOF_Z55w@mail.gmail.com>
Date: Thu, 3 Jul 2025 12:39:27 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: syzbot <syzbot+d8b58d7b0ad89a678a16@...kaller.appspotmail.com>, 
	Lion <nnamrec@...il.com>
Cc: David Miller <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, 
	Simon Horman <horms@...nel.org>, Jiri Pirko <jiri@...nulli.us>, Jakub Kicinski <kuba@...nel.org>, 
	LKML <linux-kernel@...r.kernel.org>, 
	Linux Kernel Network Developers <netdev@...r.kernel.org>, Paolo Abeni <pabeni@...hat.com>, 
	syzkaller-bugs <syzkaller-bugs@...glegroups.com>, Cong Wang <xiyou.wangcong@...il.com>
Subject: Re: Lion, can you take a look at his? WAS(Re: [syzbot] [net?] general
 protection fault in htb_qlen_notify

On Thu, Jul 3, 2025 at 11:05 AM Jamal Hadi Salim <jhs@...atatu.com> wrote:
>
> On Thu, Jul 3, 2025 at 7:32 AM syzbot
> <syzbot+d8b58d7b0ad89a678a16@...kaller.appspotmail.com> wrote:
> >
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit:    bd475eeaaf3c Merge branch '200GbE' of git://git.kernel.org..
> > git tree:       net

[..]
> It is triggered by your patch. On the first try, removing your patch
> seems to fix it.
> It may have nothing to do with your patch i.e your patch may have
> opened it up to trigger an existing bug.
> You removed that if n=0, len=0 check which earlier code was using to
> terminate the processing.
>

Ok, after some more digging - this is not a bug you caused but rather
one you exposed.
We are looking into it.

cheers,
jamal
> cheers,
> jamal