Hello,
syzbot found the following issue on:
HEAD commit: 56e6a3499e14 Merge tag 'trace-v6.13-rc5' of git://git.kern..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1607d6df980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=1c541fa8af5c9cc7
dashboard link:
https://syzkaller.appspot.com/bug?extid=8f5abc32c1b4789bddf0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [
dmitry....@gmail.com eric.s...@oracle.com jmo...@namei.org linux-i...@vger.kernel.org linux-...@vger.kernel.org linux-secu...@vger.kernel.org pa...@paul-moore.com robert...@huawei.com se...@hallyn.com zo...@linux.ibm.com]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable):
https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-56e6a349.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/13d5f705d706/vmlinux-56e6a349.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/542be4bff49c/bzImage-56e6a349.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+8f5abc...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 4096
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512).
process 'syz.0.0' launched './file1' with NULL argv: empty string added
BUG: unable to handle page fault for address: ffffff8482bbaaff
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD e73a067 P4D e73a067 PUD 0
Oops: Oops: 0010 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5318 Comm: syz.0.0 Not tainted 6.13.0-rc5-syzkaller-00006-g56e6a3499e14 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:0xffffff8482bbaaff
Code: Unable to access opcode bytes at 0xffffff8482bbaad5.
RSP: 0018:ffffc9000d42f2df EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88803481be08 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc9000d42f3a8
RBP: ffffc9000d42f6a8 R08: ffffc9000d42f3a7 R09: 0000000000000000
R10: ffffc9000d42f348 R11: fffff52001a85e75 R12: dffffc0000000000
R13: 1ffff92001a85e64 R14: 0000000000000017 R15: 0000000000000008
FS: 00007fbdc17176c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffff8482bbaad5 CR3: 0000000011e16000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ima_calc_field_array_hash+0x2e/0x440 security/integrity/ima/ima_crypto.c:628
ima_store_template security/integrity/ima/ima_api.c:112 [inline]
ima_store_measurement+0x31c/0x6f0 security/integrity/ima/ima_api.c:383
process_measurement+0x150b/0x1fb0 security/integrity/ima/ima_main.c:380
ima_bprm_check+0xfd/0x200 security/integrity/ima/ima_main.c:547
security_bprm_check+0xd2/0x250 security/security.c:1296
search_binary_handler fs/exec.c:1736 [inline]
exec_binprm fs/exec.c:1790 [inline]
bprm_execve+0xa53/0x17a0 fs/exec.c:1842
do_execveat_common+0x55f/0x6f0 fs/exec.c:1949
do_execveat fs/exec.c:2034 [inline]
__do_sys_execveat fs/exec.c:2108 [inline]
__se_sys_execveat fs/exec.c:2102 [inline]
__x64_sys_execveat+0xc4/0xe0 fs/exec.c:2102
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbdc0985d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbdc1717038 EFLAGS: 00000246 ORIG_RAX: 0000000000000142
RAX: ffffffffffffffda RBX: 00007fbdc0b75fa0 RCX: 00007fbdc0985d29
RDX: 0000000000000000 RSI: 0000000020000480 RDI: ffffffffffffff9c
RBP: 00007fbdc0a01b08 R08: 0000000000001000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fbdc0b75fa0 R15: 00007fff21c4ca28
</TASK>
Modules linked in:
CR2: ffffff8482bbaaff
---[ end trace 0000000000000000 ]---
RIP: 0010:0xffffff8482bbaaff
Code: Unable to access opcode bytes at 0xffffff8482bbaad5.
RSP: 0018:ffffc9000d42f2df EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88803481be08 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc9000d42f3a8
RBP: ffffc9000d42f6a8 R08: ffffc9000d42f3a7 R09: 0000000000000000
R10: ffffc9000d42f348 R11: fffff52001a85e75 R12: dffffc0000000000
R13: 1ffff92001a85e64 R14: 0000000000000017 R15: 0000000000000008
FS: 00007fbdc17176c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffff8482bbaad5 CR3: 0000000011e16000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup