syzbot


KASAN: stack-out-of-bounds Write in __ip_options_echo

Status: auto-closed as invalid on 2019/10/24 16:14
Reported-by: syzbot+49e4614fdbd32d63c7ad@syzkaller.appspotmail.com
First crash: 2036d, last: 2036d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 KASAN: stack-out-of-bounds Write in __ip_options_echo 1 2035d 2035d 0/1 auto-closed as invalid on 2019/10/25 08:39
upstream KASAN: stack-out-of-bounds Write in __ip_options_echo net syz done 8 2040d 2044d 12/28 fixed on 2019/05/27 12:48
upstream KASAN: stack-out-of-bounds Write in __ip_options_echo (2) net 1 1108d 1108d 0/28 closed as invalid on 2021/12/14 20:02

Sample crash report:
loop2: rw=1, want=26693, limit=112
attempt to access beyond end of device
loop2: rw=1, want=26702, limit=112
==================================================================
attempt to access beyond end of device
BUG: KASAN: stack-out-of-bounds in memcpy include/linux/string.h:347 [inline]
BUG: KASAN: stack-out-of-bounds in __ip_options_echo+0x269/0xfb0 net/ipv4/ip_options.c:123
Write of size 69 at addr ffff8880aef07b80 by task swapper/1/0

CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.114 #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x138/0x19c lib/dump_stack.c:53
 print_address_description.cold+0x7c/0x1dc mm/kasan/report.c:252
 kasan_report_error mm/kasan/report.c:351 [inline]
 kasan_report mm/kasan/report.c:409 [inline]
 kasan_report.cold+0xaf/0x2b5 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
loop2: rw=1, want=26703, limit=112
 memcpy+0x38/0x50 mm/kasan/kasan.c:303
 memcpy include/linux/string.h:347 [inline]
 __ip_options_echo+0x269/0xfb0 net/ipv4/ip_options.c:123
 __icmp_send+0x668/0x11f0 net/ipv4/icmp.c:698
attempt to access beyond end of device
loop2: rw=1, want=26704, limit=112
 ipv4_link_failure+0x233/0x460 net/ipv4/route.c:1213
attempt to access beyond end of device
loop2: rw=1, want=26705, limit=112
 dst_link_failure include/net/dst.h:442 [inline]
 arp_error_report+0xb1/0x190 net/ipv4/arp.c:297
 neigh_invalidate+0x233/0x540 net/core/neighbour.c:891
 neigh_timer_handler+0x851/0xa80 net/core/neighbour.c:977
attempt to access beyond end of device
 call_timer_fn+0x164/0x680 kernel/time/timer.c:1279
 expire_timers kernel/time/timer.c:1318 [inline]
 __run_timers kernel/time/timer.c:1634 [inline]
 __run_timers kernel/time/timer.c:1602 [inline]
 run_timer_softirq+0x5b4/0x1570 kernel/time/timer.c:1647
 __do_softirq+0x24e/0x9ae kernel/softirq.c:288
 invoke_softirq kernel/softirq.c:368 [inline]
 irq_exit+0x160/0x1b0 kernel/softirq.c:409
 exiting_irq arch/x86/include/asm/apic.h:648 [inline]
 smp_apic_timer_interrupt+0x156/0x600 arch/x86/kernel/apic/apic.c:1064
 apic_timer_interrupt+0x8e/0xa0 arch/x86/entry/entry_64.S:787
 </IRQ>
RIP: 0010:native_safe_halt+0x2/0x10 arch/x86/include/asm/irqflags.h:58
RSP: 0018:ffff8880a9d2fe70 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff10
RAX: 1ffffffff0ee2970 RBX: ffff8880a9d1c340 RCX: 0000000000000000
RDX: dffffc0000000000 RSI: 0000000000000001 RDI: ffff8880a9d1cbbc
RBP: ffff8880a9d2fe98 R08: 1ffffffff1049a01 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff87714b70
R13: 0000000000000000 R14: 0000000000000000 R15: ffff8880a9d1c340
 arch_cpu_idle+0x10/0x20 arch/x86/kernel/process.c:557
loop2: rw=1, want=30377, limit=112
 default_idle_call+0x36/0x90 kernel/sched/idle.c:98
 cpuidle_idle_call kernel/sched/idle.c:156 [inline]
 do_idle+0x262/0x3d0 kernel/sched/idle.c:246
 cpu_startup_entry+0x1b/0x20 kernel/sched/idle.c:351
 start_secondary+0x362/0x4d0 arch/x86/kernel/smpboot.c:272
 secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240

The buggy address belongs to the page:
page:ffffea0002bbc1c0 count:1 mapcount:0 mapping:          (null) index:0x0
flags: 0x1fffc0000000800(reserved)
raw: 01fffc0000000800 0000000000000000 0000000000000000 00000001ffffffff
raw: ffffea0002bbc1e0 ffffea0002bbc1e0 0000000000000000 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8880aef07a80: f2 f2 f2 00 00 00 00 f2 f2 f2 f2 00 00 00 00 00
 ffff8880aef07b00: 00 00 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 00 00
>ffff8880aef07b80: 00 00 00 00 00 f3 f3 f3 f3 00 00 00 00 00 00 00
                                  ^
 ffff8880aef07c00: 00 f1 f1 f1 f1 00 00 f3 f3 00 00 00 00 00 00 00
 ffff8880aef07c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/04/27 16:12 linux-4.14.y fa5941f45d7e b617407b .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.