syzbot


BUG: unable to handle kernel NULL pointer dereference in corrupted

Status: upstream: reported C repro on 2019/10/14 10:06
Reported-by: syzbot+f4c424b510a718452d72@syzkaller.appspotmail.com
First crash: 1865d, last: 1624d
Fix bisection the fix commit could be any of (bisect log):
  b98aebd29824 Linux 4.14.150
  56dfe6252c68 Linux 4.14.188
  
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-54 BUG: unable to handle kernel NULL pointer dereference in corrupted C 424 10d 1444d 0/2 upstream: reported C repro on 2020/12/07 19:36
upstream BUG: unable to handle kernel NULL pointer dereference in corrupted (5) C done error 3 1707d 1713d 0/28 auto-obsoleted due to no activity on 2022/09/14 04:18
linux-4.19 BUG: unable to handle kernel NULL pointer dereference in corrupted C done 6 1276d 1858d 1/1 fixed on 2021/06/24 20:09
upstream BUG: unable to handle kernel NULL pointer dereference in corrupted (4) syz done done 1 1976d 1975d 12/28 fixed on 2019/08/27 17:15
upstream BUG: unable to handle kernel NULL pointer dereference in corrupted (3) C 1 2144d 2144d 11/28 fixed on 2019/03/06 07:43
upstream BUG: unable to handle kernel NULL pointer dereference in corrupted (2) kernel C 1 2318d 2318d 8/28 fixed on 2018/08/07 13:43
upstream BUG: unable to handle kernel NULL pointer dereference in corrupted net C 5 2358d 2358d 8/28 fixed on 2018/07/09 18:05
Last patch testing requests (6)
Created Duration User Patch Repo Result
2023/01/24 11:32 12m retest repro linux-4.14.y report log
2023/01/24 10:32 14m retest repro linux-4.14.y report log
2023/01/24 09:32 10m retest repro linux-4.14.y report log
2022/09/07 04:27 8m retest repro linux-4.14.y report log
2022/09/07 03:27 9m retest repro linux-4.14.y report log
2022/09/07 02:27 8m retest repro linux-4.14.y report log
Fix bisection attempts (8)
Created Duration User Patch Repo Result
2020/07/11 03:54 30m bisect fix linux-4.14.y OK (2) job log
2020/06/11 03:29 23m bisect fix linux-4.14.y OK (0) job log log
2020/05/12 03:04 25m bisect fix linux-4.14.y OK (0) job log log
2020/04/12 02:40 23m bisect fix linux-4.14.y OK (0) job log log
2020/03/13 02:14 26m bisect fix linux-4.14.y OK (0) job log log
2020/02/12 00:57 23m bisect fix linux-4.14.y OK (0) job log log
2020/01/12 19:33 23m bisect fix linux-4.14.y OK (0) job log log
2019/12/13 19:10 23m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
audit: type=1400 audit(1572142299.544:36): avc:  denied  { map } for  pid=6997 comm="syz-executor162" path="/root/syz-executor162179496" dev="sda1" ino=16484 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
==================================================================
BUG: unable to handle kernel NULL pointer dereference
BUG: KASAN: null-ptr-deref in memcpy include/linux/string.h:347 [inline]
BUG: KASAN: null-ptr-deref in llcp_sock_getname+0x38f/0x4a0 net/nfc/llcp_sock.c:532
Read of size 3 at addr           (null) by task syz-executor162/7005
 at           (null)

IP: memcpy_erms+0x6/0x10 arch/x86/lib/memcpy_64.S:54
CPU: 0 PID: 7005 Comm: syz-executor162 Not tainted 4.14.150 #0
PGD 76fdb067 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
P4D 76fdb067 
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x138/0x197 lib/dump_stack.c:53
 kasan_report_error mm/kasan/report.c:349 [inline]
 kasan_report mm/kasan/report.c:409 [inline]
 kasan_report.cold+0x127/0x2af mm/kasan/report.c:393
 check_memory_region_inline mm/kasan/kasan.c:260 [inline]
 check_memory_region+0x123/0x190 mm/kasan/kasan.c:267
PUD a0a2f067 
 memcpy+0x24/0x50 mm/kasan/kasan.c:302
PMD 0 
 memcpy include/linux/string.h:347 [inline]
 llcp_sock_getname+0x38f/0x4a0 net/nfc/llcp_sock.c:532
Oops: 0000 [#1] PREEMPT SMP KASAN
 SYSC_getpeername+0x120/0x270 net/socket.c:1715
Modules linked in:
CPU: 1 PID: 7006 Comm: syz-executor162 Not tainted 4.14.150 #0
 SyS_getpeername+0x24/0x30 net/socket.c:1699
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880a59d0580 task.stack: ffff8880996b0000
 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
RIP: 0010:memcpy_erms+0x6/0x10 arch/x86/lib/memcpy_64.S:54
RSP: 0018:ffff8880996b7d20 EFLAGS: 00010246
 entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x441299
RAX: ffff8880996b7e0a RBX: ffff8880996b7df8 RCX: 0000000000000003
RSP: 002b:00007fff87920a38 EFLAGS: 00000246
RDX: 0000000000000003 RSI: 0000000000000000 RDI: ffff8880996b7e0a
 ORIG_RAX: 0000000000000034
RBP: ffff8880996b7d40 R08: 1ffff110132d6fc1 R09: ffffed10132d6fc2
R10: ffffed10132d6fc1 R11: ffff8880996b7e0c R12: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000441299
R13: ffff8880996b7e0a R14: 0000000000000000 R15: ffffffff87069c40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00000000006cb018 R08: 00000000004002c8 R09: 00000000004002c8
FS:  000000000251b880(0000) GS:ffff8880aef00000(0000) knlGS:0000000000000000
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000402010
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
R13: 00000000004020a0 R14: 0000000000000000 R15: 0000000000000000
CR2: 0000000000000000 CR3: 000000008cdfd000 CR4: 00000000001406e0
==================================================================
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/10/27 02:14 linux-4.14.y b98aebd29824 25bb509e .config console log report syz C ci2-linux-4-14
2019/10/17 05:05 linux-4.14.y e132c8d7b58d 8c88c9c1 .config console log report syz C ci2-linux-4-14
2019/10/14 09:05 linux-4.14.y e132c8d7b58d 2f661ec4 .config console log report syz C ci2-linux-4-14
* Struck through repros no longer work on HEAD.