syzbot
panic: Caught invalid memory access at ADDR size NUM op NUM (2)
Status:
closed as dup on 2026/08/25 15:45
Reported-by: syzbot+3ee2e2997a4123379813@syzkaller.appspotmail.com
First crash: 4d03h, last: 4d03h
Sample crash report:
panic: Caught invalid memory access at ffff800001eef738 size 8 op 0
Starting stack trace...
panic(ffffffff8463cea0) at panic+0x25b sys/kern/subr_prf.c:229
__asan_load8_noabort(ffff800001eef738) at
__asan_load8_noabort+0xde
pf_remove_if_empty_ruleset(ffff800001eef6e8) at pf_remove_if_empty_ruleset+0x5c sys/net/pf_ruleset.c:292
pfi_dynaddr_setup(ffff800001784ff8,0,1) at pfi_dynaddr_setup+0x837 sys/net/pf_if.c:508
pf_addr_setup(ffffffff85482b50,ffff800001784ff8,0) at pf_addr_setup+0x3a sys/net/pf_ioctl.c:948
pfioctl(24900,cd604404,ffff800001c5e000,2,ffff800045ff54f8) at pfioctl+0xe43e sys/net/pf_ioctl.c:2379
VOP_IOCTL(ffff800001dcb7f0,cd604404,ffff800001c5e000,2,ffff8000001194e0,ffff800045ff54f8) at VOP_IOCTL+0x131 sys/kern/vfs_vops.c:264
vn_ioctl(ffff800001de38c0,cd604404,ffff800001c5e000,ffff800045ff54f8) at vn_ioctl+0x18c sys/kern/vfs_vnops.c:537
sys_ioctl(ffff800045ff54f8,ffff80003bb704f0,ffff80003bb70460) at sys_ioctl+0x868 sys/kern/sys_generic.c:510
syscall(ffff80003bb704f0) at syscall+0x1089 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003bb704f0) at syscall+0x1089 sys/arch/amd64/amd64/trap.c:791
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x4ab667fdb60, count: 246
End of stack trace.
syncing disks...
* Struck through repros no longer work on HEAD.