linux-kernel - Re: WARNING in aa_sock_msg

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: <18091.1565647215@warthog.procyon.org.uk>
Date:   Mon, 12 Aug 2019 23:00:15 +0100
From:   David Howells <dhowells@...hat.com>
To:     Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:     dhowells@...hat.com,
        syzbot <syzbot+cda1ac91660a61b51495@...kaller.appspotmail.com>,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, linux-afs@...ts.infradead.org
Subject: Re: WARNING in aa_sock_msg_perm

Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> wrote:

> This is not AppArmor's bug. LSM modules expect that "struct socket" is not
> NULL.  For some reason, peer->local->socket became NULL. Thus, suspecting
> rxrpc's bug.
> 
> >  rxrpc_send_keepalive+0x1ff/0x940 net/rxrpc/output.c:656

I agree.  There's a further refcounting bug in the local object handling, but
it's proving annoyingly difficult to reliably reproduce.

David