On 7/28/25 01:16, Alexander Potapenko wrote:
On Mon, Jul 21, 2025 at 11:35 AM syzbot
<[email protected]> 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
