WARNING in aa_change_profile

11 views
Skip to first unread message

syzbot

unread,
Nov 11, 2020, 10:46:19 PM11/11/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 27ce4f2a Linux 4.14.206
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1624719a500000
kernel config: https://syzkaller.appspot.com/x/.config?x=32258a0e1fac372d
dashboard link: https://syzkaller.appspot.com/bug?extid=b173aa254e7452b7ad2e
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b173aa...@syzkaller.appspotmail.com

sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
------------[ cut here ]------------
WARNING: CPU: 1 PID: 32690 at security/apparmor/file.c:136 aa_audit_file.cold+0x18/0x4f security/apparmor/file.c:136
Kernel panic - not syncing: panic_on_warn set ...

__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45deb9
RSP: 002b:00007f6f41b9fc78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002e640 RCX: 000000000045deb9
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000007
RBP: 00007f6f41b9fca0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffc2c9773af R14: 00007f6f41ba09c0 R15: 000000000118bf2c
CPU: 1 PID: 32690 Comm: syz-executor.4 Not tainted 4.14.206-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
bridge_slave_0: FDB only supports static addresses
__warn.cold+0x20/0x4b kernel/panic.c:547
report_bug+0x208/0x249 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:aa_audit_file.cold+0x18/0x4f security/apparmor/file.c:136
RSP: 0018:ffff8881f38cf7d0 EFLAGS: 00010282
RAX: 0000000000000049 RBX: 1ffff1103e719efd RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff8145da90 RDI: ffffed103e719ef0
RBP: ffff8881f38cf9f8 R08: 0000000000000049 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000fffffff4
R13: ffff88823f8b8d80 R14: ffff8881f38cf848 R15: 0000000000000000
aa_change_profile+0xcc9/0x2420 security/apparmor/domain.c:1277
apparmor_setprocattr+0x98c/0xa80 security/apparmor/lsm.c:651
security_setprocattr+0x74/0xb0 security/security.c:1272
proc_pid_attr_write+0x1bd/0x280 fs/proc/base.c:2588
__vfs_write+0xe4/0x630 fs/read_write.c:480
vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45deb9
RSP: 002b:00007fda31191c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000003a840 RCX: 000000000045deb9
RDX: 000000000000008b RSI: 0000000020000140 RDI: 0000000000000005
RBP: 00007fda31191ca0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff0fedc87f R14: 00007fda311929c0 R15: 000000000118bf2c
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Aug 29, 2021, 3:30:16 AM8/29/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages