linux-kernel - Re: [syzbot] [apparmor?] linux-next test error: WARNING in apparmor_unix_stream

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: <2a6074ec-59ca-49af-87e8-d468cffc4a87@canonical.com>
Date: Wed, 30 Jul 2025 03:17:52 -0700
From: John Johansen <john.johansen@...onical.com>
To: Alexander Potapenko <glider@...gle.com>
Cc: apparmor@...ts.ubuntu.com, jmorris@...ei.org, john@...armor.net,
 linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
 linux-security-module@...r.kernel.org, paul@...l-moore.com,
 serge@...lyn.com, sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [apparmor?] linux-next test error: WARNING in
 apparmor_unix_stream_connect

On 7/28/25 01:16, Alexander Potapenko wrote:
> On Mon, Jul 21, 2025 at 11:35 AM syzbot
> <syzbot+cd38ee04bcb3866b0c6d@...kaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
> 
> John, do you have an idea what's going on?
> This is pretty likely to be related to your "apparmor: make sure unix
> socket labeling is correctly updated." patch.

yeah it is being caused by that patch. Specifically it introduces using
security_sk_alloc() to make sure the sk is given a default label which
makes this check now incorrect the fix is just to drop the check. I have
added the fix with the syzbot ref