lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000c3c84605b98d88f9@google.com>
Date:   Sat, 23 Jan 2021 01:00:19 -0800
From:   syzbot <syzbot+71ce453661898ec7a122@...kaller.appspotmail.com>
To:     andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
        daniel@...earbox.net, davem@...emloft.net, hawk@...nel.org,
        john.fastabend@...il.com, kafai@...com, kpsingh@...nel.org,
        kuba@...nel.org, linux-kernel@...r.kernel.org, mingo@...hat.com,
        netdev@...r.kernel.org, rostedt@...dmis.org, songliubraving@...com,
        syzkaller-bugs@...glegroups.com, yhs@...com
Subject: BUG: unable to handle kernel paging request in bpf_trace_run7

Hello,

syzbot found the following issue on:

HEAD commit:    7d68e382 bpf: Permit size-0 datasec
git tree:       bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17a5a184d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e0c7843b8af99dff
dashboard link: https://syzkaller.appspot.com/bug?extid=71ce453661898ec7a122
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+71ce453661898ec7a122@...kaller.appspotmail.com

BUG: unable to handle page fault for address: ffffc90000cc0030
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 10000067 
P4D 10000067 
PUD 101ab067 
PMD 10a9e067 
PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8498 Comm: syz-executor.3 Not tainted 5.11.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:bpf_dispatcher_nop_func include/linux/bpf.h:651 [inline]
RIP: 0010:__bpf_trace_run kernel/trace/bpf_trace.c:2088 [inline]
RIP: 0010:bpf_trace_run7+0x174/0x420 kernel/trace/bpf_trace.c:2130
Code: f7 ff 48 8d 7b 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 a1 02 00 00 48 8d 73 38 48 8d 7c 24 28 <ff> 53 30 e8 14 0b f7 ff e8 af 33 7e 07 31 ff 89 c3 89 c6 e8 84 12
RSP: 0018:ffffc900019cf300 EFLAGS: 00010282

RAX: 0000000000000000 RBX: ffffc90000cc0000 RCX: ffffffff817bd211
RDX: 0000000000000000 RSI: ffffc90000cc0038 RDI: ffffc900019cf328
RBP: 1ffff92000339e61 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff817bd17f R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000001000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000002f78940(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000cc0030 CR3: 00000000533d3000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
 __bpf_trace_percpu_alloc_percpu+0x1dc/0x220 include/trace/events/percpu.h:10
 trace_percpu_alloc_percpu include/trace/events/percpu.h:10 [inline]
 pcpu_alloc+0xba6/0x16f0 mm/percpu.c:1844
 xt_percpu_counter_alloc+0x131/0x1a0 net/netfilter/x_tables.c:1820
 find_check_entry.constprop.0+0xab/0x9a0 net/ipv4/netfilter/ip_tables.c:527
 translate_table+0xc26/0x16a0 net/ipv4/netfilter/ip_tables.c:717
 do_replace net/ipv4/netfilter/ip_tables.c:1135 [inline]
 do_ipt_set_ctl+0x553/0xb50 net/ipv4/netfilter/ip_tables.c:1627
 nf_setsockopt+0x83/0xe0 net/netfilter/nf_sockopt.c:101
 ip_setsockopt+0x3c3/0x3a20 net/ipv4/ip_sockglue.c:1435
 tcp_setsockopt+0x136/0x2440 net/ipv4/tcp.c:3597
 __sys_setsockopt+0x2db/0x610 net/socket.c:2115
 __do_sys_setsockopt net/socket.c:2126 [inline]
 __se_sys_setsockopt net/socket.c:2123 [inline]
 __x64_sys_setsockopt+0xba/0x150 net/socket.c:2123
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x460d4a
Code: 49 89 ca b8 37 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 ca 88 fb ff c3 66 0f 1f 84 00 00 00 00 00 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 aa 88 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007fff6bb05e38 EFLAGS: 00000202 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007fff6bb05e60 RCX: 0000000000460d4a
RDX: 0000000000000040 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 000000000074ee60 R08: 00000000000002d8 R09: 0000000000004000
R10: 000000000074cd00 R11: 0000000000000202 R12: 00007fff6bb05ec0
R13: 0000000000000003 R14: 000000000074cca0 R15: 0000000000000000
Modules linked in:
CR2: ffffc90000cc0030
---[ end trace 16413316cc5dacf7 ]---
RIP: 0010:bpf_dispatcher_nop_func include/linux/bpf.h:651 [inline]
RIP: 0010:__bpf_trace_run kernel/trace/bpf_trace.c:2088 [inline]
RIP: 0010:bpf_trace_run7+0x174/0x420 kernel/trace/bpf_trace.c:2130
Code: f7 ff 48 8d 7b 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 a1 02 00 00 48 8d 73 38 48 8d 7c 24 28 <ff> 53 30 e8 14 0b f7 ff e8 af 33 7e 07 31 ff 89 c3 89 c6 e8 84 12
RSP: 0018:ffffc900019cf300 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffc90000cc0000 RCX: ffffffff817bd211
RDX: 0000000000000000 RSI: ffffc90000cc0038 RDI: ffffc900019cf328
RBP: 1ffff92000339e61 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff817bd17f R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000001000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000002f78940(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000cc0030 CR3: 00000000533d3000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600


---
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 syzkaller@...glegroups.com.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ