Hello,
syzbot found the following issue on:
HEAD commit: 5b7a52cd Linux 4.14.202
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=143d4fd8500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=fa386e02ca459165
dashboard link:
https://syzkaller.appspot.com/bug?extid=5e926a1a083ff8f14ceb
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+5e926a...@syzkaller.appspotmail.com
RBP: 00007fa0ad6a7ca0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffea9173e4f R14: 00007fa0ad6a89c0 R15: 000000000118bf2c
AppArmor WARN aa_audit_file: ((!((&sa)->apparmor_audit_data)->request)):
------------[ cut here ]------------
WARNING: CPU: 1 PID: 24906 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 ...
CPU: 1 PID: 24906 Comm: syz-executor.4 Not tainted 4.14.202-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
__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:ffff8880954bf7d0 EFLAGS: 00010282
RAX: 0000000000000049 RBX: 1ffff11012a97efd RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff8145d8d0 RDI: ffffed1012a97ef0
RBP: ffff8880954bf9f8 R08: 0000000000000049 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000fffffff4
R13: ffff88823f8b8d80 R14: ffff8880954bf848 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:2589
__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:0x45de59
RSP: 002b:00007fa0ad6a7c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000003a7c0 RCX: 000000000045de59
RDX: 0000000000000031 RSI: 00000000200002c0 RDI: 0000000000000003
RBP: 00007fa0ad6a7ca0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffea9173e4f R14: 00007fa0ad6a89c0 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.