netdev - Re: memory leak in tcindex_set

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: <20200204.222245.1920371518669295397.davem@davemloft.net>
Date:   Tue, 04 Feb 2020 22:22:45 +0100 (CET)
From:   David Miller <davem@...emloft.net>
To:     eric.dumazet@...il.com
Cc:     syzbot+f0bbb2287b8993d4fa74@...kaller.appspotmail.com,
        jhs@...atatu.com, jiri@...nulli.us, kuba@...nel.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, xiyou.wangcong@...il.com
Subject: Re: memory leak in tcindex_set_parms

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Tue, 4 Feb 2020 10:03:16 -0800

> 
> 
> On 2/4/20 9:58 AM, syzbot wrote:
>> Hello,
>> 
>> syzbot found the following crash on:
>> 
>> HEAD commit:    322bf2d3 Merge branch 'for-5.6' of git://git.kernel.org/pu..
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1111f8e6e00000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=8d0490614a000a37
>> dashboard link: https://syzkaller.appspot.com/bug?extid=f0bbb2287b8993d4fa74
>> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17db90f6e00000
>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13a94511e00000
>> 
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+f0bbb2287b8993d4fa74@...kaller.appspotmail.com
>> 
>>
> 
> Might have been fixed already ?
> 
> commit 599be01ee567b61f4471ee8078870847d0a11e8e    net_sched: fix an OOB access in cls_tcindex

My reaction was actually that this bug is caused by this commit :)