syzbot


SYZFAIL: tun: can't open device (6)

Status: upstream: reported on 2025/06/22 13:40
Reported-by: syzbot+39360db8516b9e181809@syzkaller.appspotmail.com
First crash: 71d, last: 30d
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd SYZFAIL: tun: can't open device (2) -1 1 1500d 1500d 0/3 auto-closed as invalid on 2021/10/22 18:00
openbsd SYZFAIL: tun: can't open device (3) -1 86 1326d 1326d 0/3 closed as invalid on 2022/01/15 08:41
openbsd SYZFAIL: tun: can't open device (5) -1 82 177d 192d 0/3 auto-obsoleted due to no activity on 2025/04/27 11:29
openbsd SYZFAIL: tun: can't open device -1 syz 4 1642d 1642d 3/3 fixed on 2021/03/10 05:59
openbsd SYZFAIL: tun: can't open device (4) -1 8 316d 417d 0/3 auto-obsoleted due to no activity on 2025/01/18 18:59

Sample crash report:
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap5 (errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
 (errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
 (errno 16: Device busy)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
ifconfig: socket: No buffer space available
ifconfig: socket: No buffer space available
SYZFAIL: command failed
command=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ifconfig tap5 lladdr aa:aa:aa:aa:aa:aa: 256 (errno 1: Operation not permitted)
SYZFAIL: repeatedly failed to execute the program
proc=5 req=2238 state=1 status=67 (errno 4: Interrupted system call)

OpenBSD/amd64 (YLF&ʐ)?9ɩRmȼn2j]V5_';aG[-׹ѹye@|AR0"	) (tty00)

login: uvn_flush: obj=0xfffffd806be829d0, offset=0x3ff000.  error during pageout.
uvn_flush: WARNING: changes to page may be lost!
set $lines = 0
Password:
Login incorrect
login: show panic
Password:
Login incorrect
login: show registers
Password:
Login incorrect
login: ps
Password:
Login incorrect
show malloc
login: Password:

Crashes (31):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/02 09:12 openbsd 4c5c4401a4d8 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/17 01:54 openbsd 9ce74a582983 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/16 16:35 openbsd 054bb2fd459c 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/16 00:30 openbsd 86f69b9e7bb3 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/15 19:16 openbsd feb5a82c5bff 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/15 16:44 openbsd feb5a82c5bff 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/15 10:33 openbsd feb5a82c5bff 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/14 15:28 openbsd 40f26cfbae82 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/14 02:50 openbsd 79bd20f69ae4 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/13 11:24 openbsd 5bd8d26974b4 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/11 09:49 openbsd 0b4ddc31a5ae 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/11 09:49 openbsd 0b4ddc31a5ae 3cda49cf .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/10 19:47 openbsd 3cb786741c54 d7384b6d .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/09 23:04 openbsd e91e1a12e0dd 956bd956 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/07/09 15:17 openbsd e91e1a12e0dd 956bd956 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/09 10:04 openbsd bc55f572b2c5 f4e5e155 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/09 09:56 openbsd bc55f572b2c5 f4e5e155 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/09 05:45 openbsd bc55f572b2c5 f4e5e155 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/06 05:08 openbsd f2b2329d6987 4f67c4ae .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/05 01:02 openbsd 184f8edada4a 4f67c4ae .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/02 10:33 openbsd 15da244b1a00 bc80e4f0 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/07/01 10:59 openbsd 03190a0c50a7 6e83b42d .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/29 00:08 openbsd fd1ffb313c1e fc9d8ee5 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/28 03:14 openbsd d7bdfee22977 fc9d8ee5 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/27 23:10 openbsd d7bdfee22977 fc9d8ee5 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/27 08:45 openbsd 69432c0dafb3 803ce19b .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/27 03:11 openbsd 69432c0dafb3 803ce19b .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/26 20:51 openbsd 0f21a7ba35b8 1ae8177e .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/26 07:12 openbsd c04c22679fb3 26d77996 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/23 09:22 openbsd bfd2b5c81cd0 d6cdfb8a .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/06/22 13:39 openbsd cb7d86176520 d6cdfb8a .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
* Struck through repros no longer work on HEAD.