KASAN: invalid memory access in arprequest

0 views
Skip to first unread message

syzbot

unread,
Nov 16, 2026, 6:09:55 AM (4 days ago) Nov 16
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 720393356b05 Bound major(rdev) before indexing cdevsw[] in..
git tree: https://github.com/blackgnezdo/openbsd-src.git syzbot-kasan
console output: https://syzkaller.appspot.com/x/log.txt?x=16a6764d580000
kernel config: https://syzkaller.appspot.com/x/.config?x=85e25e37d09e1b88
dashboard link: https://syzkaller.appspot.com/bug?extid=49e574c357cc1bdb4c35

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/626f02d9ff9f/disk-72039335.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/c0031ec9c782/bsd-72039335.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fbe9cf4333ca/kernel-72039335.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+49e574...@syzkaller.appspotmail.com

KASAN: invalid read of 6 bytes at 0xffff800001cdbc26 from pc 0xffffffff82b6b86e
KASAN: first bad byte at 0xffff800001cdbc26 (+0); shadow 0xfc: malloc use-after-free
KASAN: 0xffff800001cdbc26 is 38 bytes inside the 64-byte malloc slot [0xffff800001cdbc00..0xffff800001cdbc40)
KASAN: allocated at:
#0 malloc+0x104a sys/kern/kern_malloc.c:490
#1 amap_alloc1+0x39f sys/uvm/uvm_amap.c:356
#2 amap_alloc+0xa3 sys/uvm/uvm_amap.c:-1
#3 amap_copy+0xbb9 sys/uvm/uvm_amap.c:570
#4 uvm_fault_check+0x763 sys/uvm/uvm_fault.c:747
#5 uvm_fault+0x2d4 sys/uvm/uvm_fault.c:-1
#6 upageflttrap+0xea sys/arch/amd64/amd64/trap.c:194
#7 usertrap+0x55d sys/arch/amd64/amd64/trap.c:661
#8 recall_trap+0x8
KASAN: freed at:
#0 free+0x400 kasan_quarantine_push sys/kern/kern_malloc.c:164 [inline]
#0 free+0x400 sys/kern/kern_malloc.c:664
#1 amap_free+0x2cb sys/uvm/uvm_amap.c:454
#2 uvm_unmap_detach+0xf6 sys/uvm/uvm_map.c:1359
#3 uvm_map_teardown+0x573 sys/uvm/uvm_map.c:2535
#4 exit1+0xa38 sys/kern/kern_exit.c:260
#5 sys_exit+0x4a
#6 syscall+0x118e mi_syscall sys/sys/syscall_mi.h:176 [inline]
#6 syscall+0x118e sys/arch/amd64/amd64/trap.c:804
#7 Xsyscall+0x128
KASAN: pc: arprequest+0x27e
KASAN: call trace:
#0 kasan_memcpy+0x170 kasan_shadow_check sys/kern/subr_kasan.c:1014 [inline]
#0 kasan_memcpy+0x170 sys/kern/subr_kasan.c:1024
#1 arprequest+0x27e sys/netinet/if_ether.c:326
#2 arp_rtrequest+0x63f sys/netinet/if_ether.c:226
#3 rtrequest+0x1625 sys/net/route.c:1110
#4 rtm_output+0xca1 sys/net/rtsock.c:956
#5 route_output+0xf1e sys/net/rtsock.c:862
#6 route_send+0xdd sys/net/rtsock.c:322
#7 sosend+0xb45 sys/kern/uipc_socket.c:-1
#8 sendit+0x9e5 sys/kern/uipc_syscalls.c:785
#9 sys_sendto+0x192 sys/kern/uipc_syscalls.c:563
#10 syscall+0x118e mi_syscall sys/sys/syscall_mi.h:176 [inline]
#10 syscall+0x118e sys/arch/amd64/amd64/trap.c:804
#11 Xsyscall+0x128
KASAN: shadow of 0xffff800001cdbb00..0xffff800001cdbd80 (1 cell = 8 bytes):
0xffff800001cdbb00: fc fc fc fc fc fc fc fc 08 08 08 08 fb fc fc fc
0xffff800001cdbb80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>0xffff800001cdbc00: fc fc fc fc[fc]fc fc fc fc fc fc fc fc fc fc fc
0xffff800001cdbc80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
0xffff800001cdbd00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
KASAN: legend: 00 valid; 01..07 partial; fb malloc redzone; fc malloc freed; fd pool freed; fe kmem; fa global; f1..f4/f8 stack/scope
panic: Caught invalid memory access at ffff800001cdbc26 size 6 op 0
Starting stack trace...
panic(ffffffff847c943c) at panic+0x281 sys/kern/subr_prf.c:229
kasan_memcpy(ffff800039edc2a8,ffff800001cdbc26,6) at kasan_memcpy+0x18f kasan_shadow_check sys/kern/subr_kasan.c:1002 [inline]
kasan_memcpy(ffff800039edc2a8,ffff800001cdbc26,6) at kasan_memcpy+0x18f sys/kern/subr_kasan.c:1025
arprequest(ffff800000176858,ffff800001bbc244,ffff800001bbc244,ffff800001cdbc26) at arprequest+0x27e sys/netinet/if_ether.c:326
arp_rtrequest(ffff800000176858,1,ffff800001c7b650) at arp_rtrequest+0x63f sys/netinet/if_ether.c:226
rtrequest(1,ffff800039edc7c0,0,ffff800039edc640,16) at rtrequest+0x1625 sys/net/route.c:1110
rtm_output(ffff8000003eec00,ffff800039edc7a0,ffff800039edc7c0,0,16) at rtm_output+0xca1 sys/net/rtsock.c:956
route_output(fffffd8065ccb900,ffff80000191abd0) at route_output+0xf1e sys/net/rtsock.c:862
route_send(ffff80000191abd0,fffffd8065ccb900,0,0) at route_send+0xdd sys/net/rtsock.c:322
sosend(ffff80000191abd0,0,ffff800039edcb80,0,0,80c) at sosend+0xb45 sys/kern/uipc_socket.c:-1
sendit(ffff80002989bc98,3,ffff800039edcd00,80c,ffff800039edcee0) at sendit+0x9e5 sys/kern/uipc_syscalls.c:785
sys_sendto(ffff80002989bc98,ffff800039edcf80,ffff800039edcee0) at sys_sendto+0x192 sys/kern/uipc_syscalls.c:563
syscall(ffff800039edcf80) at syscall+0x118e mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff800039edcf80) at syscall+0x118e sys/arch/amd64/amd64/trap.c:804
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x389845047e0, count: 244
End of stack trace.
syncing disks...


---
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
Reply all
Reply to author
Forward
0 new messages