linux-kernel - RE: general protection fault in dst_dev

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]

Date:   Wed, 20 Mar 2019 15:43:49 +0000
From:   Jon Maloy <jon.maloy@...csson.com>
To:     syzbot <syzbot+9d4c12bfd45a58738d0a@...kaller.appspotmail.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "dsahern@...il.com" <dsahern@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "pablo@...filter.org" <pablo@...filter.org>,
        "syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
        "tipc-discussion@...ts.sourceforge.net" 
        <tipc-discussion@...ts.sourceforge.net>,
        "ying.xue@...driver.com" <ying.xue@...driver.com>
Subject: RE: general protection fault in dst_dev_put (2)

This one points to a bug that was fixed in commit dc4501ff2875 ("tipc: fix a double free in tipc_enable_bearer()"). 
That commit was applied to 4.20, but is not present in 4.16, which caused this dump. 
To get further with this I need a dump of the actual crash in 4.20 or 5.0.
Maybe we are looking at two different problems here?

///jon



> -----Original Message-----
> From: netdev-owner@...r.kernel.org <netdev-owner@...r.kernel.org>
> On Behalf Of syzbot
> Sent: 19-Mar-19 18:24
> To: davem@...emloft.net; dsahern@...il.com; Jon Maloy
> <jon.maloy@...csson.com>; linux-kernel@...r.kernel.org;
> netdev@...r.kernel.org; pablo@...filter.org; syzkaller-
> bugs@...glegroups.com; tipc-discussion@...ts.sourceforge.net;
> ying.xue@...driver.com
> Subject: Re: general protection fault in dst_dev_put (2)
> 
> syzbot has bisected this bug to:
> 
> commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
> Author: Jon Maloy <jon.maloy@...csson.com>
> Date:   Thu Mar 22 19:42:52 2018 +0000
> 
>      tipc: obtain node identity from interface by default
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1631fc2b200000
> start commit:   52dfae5c tipc: obtain node identity from interface by defa..
> git tree:       upstream
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=1531fc2b200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1131fc2b200000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8f00801d7b7c4fe6
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=9d4c12bfd45a58738d0a
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17254878c00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=171ca5df400000
> 
> Reported-by: syzbot+9d4c12bfd45a58738d0a@...kaller.appspotmail.com
> Fixes: 52dfae5c ("tipc: obtain node identity from interface by default")