BUG: unable to handle kernel paging request in kfree

Sett 10 ganger
Hopp til første uleste melding

syzbot

ulest,
4. des. 2017, 02:22:0304.12.2017
til syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
4131d5166185d0d75b5f1d4bf362a9e0bac05598
git://git.cmpxchg.org/linux-mmots.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.
CC: [an...@enomsg.org ccr...@android.com epa...@parisplace.org
james.l...@oracle.com kees...@chromium.org
linux-...@vger.kernel.org linux-secu...@vger.kernel.org
pa...@paul-moore.com s...@tycho.nsa.gov sel...@tycho.nsa.gov
se...@hallyn.com tony...@intel.com]

BUG: unable to handle kernel paging request at 0000000029c26c61
IP: kfree+0x12/0x250 mm/slab.c:3797
PGD 5e28067 P4D 5e28067 PUD 5e2a067 PMD 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 6058 Comm: syz-executor1 Not tainted 4.15.0-rc1-mm1+ #29
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: 000000004fe27047 task.stack: 000000008e11646a
RIP: 0010:kfree+0x12/0x250 mm/slab.c:3797
RSP: 0018:ffff8801db507838 EFLAGS: 00010206
RAX: ffff8801d18cc000 RBX: ffff8801d0ba4980 RCX: ffffffff821df8a8
RDX: 0000000000000100 RSI: 000000004980ab49 RDI: ffff8801d0ba4980
RBP: ffff8801db507858 R08: 0000000000000001 R09: 0000000000000002
R10: 0000000000000000 R11: ffffffff8748cda0 R12: ffff8801d0ba4980
R13: ffffffff821df8b8 R14: 1ffff1003b6a0f1b R15: ffff8801db507958
FS: 00007fcdab0f4700(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 00000001d905c000 CR4: 00000000001426e0
Call Trace:
<IRQ>
selinux_cred_free+0x48/0x70 security/selinux/hooks.c:3815
security_cred_free+0x48/0x80 security/security.c:995
put_cred_rcu+0x106/0x400 kernel/cred.c:117
__rcu_reclaim kernel/rcu/rcu.h:172 [inline]
rcu_do_batch kernel/rcu/tree.c:2674 [inline]
invoke_rcu_callbacks kernel/rcu/tree.c:2933 [inline]
__rcu_process_callbacks kernel/rcu/tree.c:2900 [inline]
rcu_process_callbacks+0xd74/0x17d0 kernel/rcu/tree.c:2917
__do_softirq+0x29d/0xbb2 kernel/softirq.c:285
invoke_softirq kernel/softirq.c:365 [inline]
irq_exit+0x1d3/0x210 kernel/softirq.c:405
exiting_irq arch/x86/include/asm/apic.h:540 [inline]
smp_apic_timer_interrupt+0x16b/0x700 arch/x86/kernel/apic/apic.c:1052
apic_timer_interrupt+0xa9/0xb0 arch/x86/entry/entry_64.S:907
</IRQ>
RIP: 0010:preempt_count arch/x86/include/asm/preempt.h:23 [inline]
RIP: 0010:check_kcov_mode kernel/kcov.c:67 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x14/0x50 kernel/kcov.c:101
RSP: 0018:ffff8801d3acecd0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff11
RAX: ffff8801d18cc000 RBX: 0000000000001000 RCX: ffffffff819a3a3f
RDX: 0000000080000001 RSI: ffffea0006c563c0 RDI: ffff8801d3acf30c
RBP: ffff8801d3acecd0 R08: ffffffff85f44cc0 R09: 1ffff1003a759d28
R10: ffff8801d18cc000 R11: 0000000000000001 R12: ffff8801d3acf288
R13: ffffea0006c563c0 R14: ffffea0006c563c0 R15: 0000000000000002
__tlb_remove_page_size+0x94/0x4e0 mm/memory.c:310
__tlb_remove_page include/asm-generic/tlb.h:150 [inline]
zap_pte_range mm/memory.c:1337 [inline]
zap_pmd_range mm/memory.c:1438 [inline]
zap_pud_range mm/memory.c:1467 [inline]
zap_p4d_range mm/memory.c:1488 [inline]
unmap_page_range+0x10e4/0x22e0 mm/memory.c:1509
unmap_single_vma+0x15f/0x2d0 mm/memory.c:1554
unmap_vmas+0xf1/0x1b0 mm/memory.c:1584
exit_mmap+0x232/0x530 mm/mmap.c:3020
__mmput kernel/fork.c:972 [inline]
mmput+0x223/0x6c0 kernel/fork.c:993
exit_mm kernel/exit.c:544 [inline]
do_exit+0x90a/0x1ae0 kernel/exit.c:856
do_group_exit+0x149/0x400 kernel/exit.c:972
get_signal+0x73f/0x16c0 kernel/signal.c:2335
do_signal+0x94/0x1ee0 arch/x86/kernel/signal.c:809
exit_to_usermode_loop+0x214/0x310 arch/x86/entry/common.c:158
prepare_exit_to_usermode arch/x86/entry/common.c:195 [inline]
syscall_return_slowpath+0x490/0x550 arch/x86/entry/common.c:264
entry_SYSCALL_64_fastpath+0x94/0x96
RIP: 0033:0x4529d9
RSP: 002b:00007fcdab0f3ce8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00000000007581b8 RCX: 00000000004529d9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000007581b8
RBP: 00000000007581b8 R08: 000000000000045a R09: 0000000000758190
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000a6f7ff R14: 00007fcdab0f49c0 R15: 0000000000000002
Code: 1b ff ff ff 48 8b 15 fe 19 3c 04 e9 57 ff ff ff 66 0f 1f 84 00 00 00
00 00 55 48 89 e5 41 56 41 55 41 54 53 48 89 fb 4c 8b 6d 08 <cc> 1f 44 00
00 65 8b 05 d2 8a 5a 7e 89 c0 48 0f a3 05 d8 23 b8
RIP: kfree+0x12/0x250 mm/slab.c:3797 RSP: ffff8801db507838
CR2: fffffffffffffff8
---[ end trace 6a87f78806f39c6d ]---


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log

Dmitry Vyukov

ulest,
6. des. 2017, 07:41:0906.12.2017
til syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
happened once, looks like corrupted heap

#syz invalid

On Mon, Dec 4, 2017 at 8:22 AM, syzbot
<bot+f2fe32d70e80730e5d...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a11440c8011869c055f7e9350%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Svar alle
Svar til forfatter
Videresend
0 nye meldinger