panic: Caught invalid memory access at ffff8000110bfc38 size 8 op 0
Stopped at      db_enter+0x17:  popq    %rbp
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*408882  85481      0           0  0x4000000    1K syz-executor
db_enter() at db_enter+0x17 sys/arch/amd64/amd64/db_interface.c:457
panic(ffffffff8463cea0) at panic+0x270 sys/kern/subr_prf.c:198
__asan_load8_noabort(ffff8000110bfc38) at __asan_load8_noabort+0xde kasan_shadow_check sys/kern/subr_kasan.c:-1 [inline]
__asan_load8_noabort(ffff8000110bfc38) at __asan_load8_noabort+0xde sys/kern/subr_kasan.c:1099
pf_remove_if_empty_ruleset(ffff8000110bfbe8) at pf_remove_if_empty_ruleset+0x5c sys/net/pf_ruleset.c:292
pfi_dynaddr_setup(ffff800001787538,0,1) at pfi_dynaddr_setup+0x837 sys/net/pf_if.c:508
pf_addr_setup(ffffffff85482b50,ffff800001787538,0) at pf_addr_setup+0x3a sys/net/pf_ioctl.c:948
pfioctl(14900,cd604404,ffff800001827000,2,ffff800029970030) at pfioctl+0xe43e sys/net/pf_ioctl.c:2379
VOP_IOCTL(ffff800001c84ea0,cd604404,ffff800001827000,2,ffff800000119548,ffff800029970030) at VOP_IOCTL+0x131 sys/kern/vfs_vops.c:264
vn_ioctl(ffff80000180cc88,cd604404,ffff800001827000,ffff800029970030) at vn_ioctl+0x18c sys/kern/vfs_vnops.c:537
sys_ioctl(ffff800029970030,ffff80003ab27f60,ffff80003ab27ec0) at sys_ioctl+0x868 sys/kern/sys_generic.c:510
syscall(ffff80003ab27f60) at syscall+0x1089 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003ab27f60) at syscall+0x1089 sys/arch/amd64/amd64/trap.c:791
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x5868a278900, count: 3
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb{1}> 
ddb{1}>