syzbot

 sign-in | mailing list | source | docs
🐞 Open [108]
🐞 Fixed [288]
🐞 Invalid [878]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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

Status: auto-obsoleted due to no activity on 2025/04/27 11:29
Reported-by: syzbot+7a9c5de91daba5133ee2@syzkaller.appspotmail.com
First crash: 124d, last: 109d
▶ ▼ Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd SYZFAIL: tun: can't open device (2) 1 1431d 1431d 0/3 auto-closed as invalid on 2021/10/22 18:00
openbsd SYZFAIL: tun: can't open device (6) 2 2d05h 3d00h 0/3 upstream: reported on 2025/06/22 13:40
openbsd SYZFAIL: tun: can't open device (3) 86 1257d 1257d 0/3 closed as invalid on 2022/01/15 08:41
openbsd SYZFAIL: tun: can't open device syz 4 1574d 1574d 3/3 fixed on 2021/03/10 05:59
openbsd SYZFAIL: tun: can't open device (4) 8 247d 349d 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/tap6 (errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
 (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
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (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/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
SYZFAIL: repeatedly failed to execute the program
proc=6 req=7 state=1 status=67 (errno 4: Interrupted system call)


OpenBSD/amd64 (Amnesiac) (tty00)

login: 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:
Login incorrect

Crashes (82):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/08 11:29 openbsd 083866324387 7e3bd60d .config console log report ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/03/02 03:07 openbsd 7ab92fbecd20 c3901742 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/03/02 02:12 openbsd 7ab92fbecd20 c3901742 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/03/01 15:14 openbsd 7ab92fbecd20 c3901742 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/03/01 00:31 openbsd cdc7fda40d13 67cf5345 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/28 23:12 openbsd 190029b2710e 1e7a43e1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/28 21:54 openbsd 190029b2710e 1e7a43e1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/28 19:57 openbsd 190029b2710e 1e7a43e1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/28 01:15 openbsd e4fd48a4b5c3 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 22:10 openbsd e4fd48a4b5c3 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 21:03 openbsd e4fd48a4b5c3 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 19:51 openbsd e4fd48a4b5c3 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 16:53 openbsd d989f921cc32 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 12:52 openbsd d989f921cc32 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 07:53 openbsd d989f921cc32 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 06:44 openbsd d989f921cc32 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 04:12 openbsd 141662745973 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/27 01:51 openbsd 141662745973 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 23:14 openbsd 141662745973 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 21:56 openbsd 141662745973 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 19:38 openbsd 141662745973 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 17:19 openbsd 141662745973 6a8fcbc4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 11:14 openbsd f92cb8f5ed1c d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 10:05 openbsd f92cb8f5ed1c d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 06:06 openbsd f92cb8f5ed1c d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 02:49 openbsd 0e50c489d79b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/26 01:06 openbsd 0e50c489d79b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 19:31 openbsd 0e50c489d79b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 18:12 openbsd 0e50c489d79b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 16:48 openbsd 0e50c489d79b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 11:23 openbsd 0f757f3da31b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 10:48 openbsd 0f757f3da31b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 06:36 openbsd 0f757f3da31b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 06:15 openbsd 0f757f3da31b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 05:00 openbsd 0f757f3da31b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/25 02:55 openbsd 0f757f3da31b d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 23:55 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 22:09 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 20:27 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 19:48 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 18:35 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 18:01 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/24 17:27 openbsd eda3d7dc1957 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 23:22 openbsd a5c838d89587 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 23:21 openbsd a5c838d89587 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 21:34 openbsd c8d1658b9cef d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 20:02 openbsd c8d1658b9cef d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 15:47 openbsd c8d1658b9cef d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 15:17 openbsd c8d1658b9cef d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/23 12:43 openbsd c8d1658b9cef d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/02/20 22:34 openbsd e17cfef6a95f 0808a665 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
* Struck through repros no longer work on HEAD.