syzbot

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

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

Status: upstream: reported on 2025/10/07 22:59
Reported-by: syzbot+5b4a2a90d1e5ea8e82e0@syzkaller.appspotmail.com
First crash: 64d, last: 20h56m
▶ ▼ Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd SYZFAIL: tun: can't open device (2) -1 1 1600d 1600d 0/3 auto-closed as invalid on 2021/10/22 18:00
openbsd SYZFAIL: tun: can't open device (6) -1 31 131d 171d 0/3 auto-obsoleted due to no activity on 2025/09/21 09:12
openbsd SYZFAIL: tun: can't open device (3) -1 86 1426d 1426d 0/3 closed as invalid on 2022/01/15 08:41
openbsd SYZFAIL: tun: can't open device (5) -1 82 278d 293d 0/3 auto-obsoleted due to no activity on 2025/04/27 11:29
openbsd SYZFAIL: tun: can't open device -1 syz 4 1743d 1743d 3/3 fixed on 2021/03/10 05:59
openbsd SYZFAIL: tun: can't open device (4) -1 8 416d 518d 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/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap2 (errno 16: Device busy)
SYZFAIL: repeatedly failed to execute the program
proc=2 req=3 state=1 status=67 (errno 4: Interrupted system call)
uvn_flush: obj=0xfffffd806f72d968, offset=0x3ff000.  error during pageout.
uvn_flush: WARNING: changes to page may be lost!

Crashes (103):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/10 15:59 openbsd f5c5b16722b5 48b27acc .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/10 08:58 openbsd f5c5b16722b5 48b27acc .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/10 07:12 openbsd f5c5b16722b5 48b27acc .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/10 00:31 openbsd 9bea02201100 fc20f974 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/09 15:01 openbsd bf8f637750de fc20f974 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/07 19:16 openbsd 55a34bd78c86 cee4cb10 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/05 17:37 openbsd 4f07d5022fc4 cee4cb10 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/05 15:59 openbsd 4f07d5022fc4 cee4cb10 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/05 14:58 openbsd 4f07d5022fc4 cee4cb10 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/05 05:45 openbsd 9dbbe670f20c cee4cb10 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/03 23:59 openbsd 4ae131efb048 cee4cb10 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/02 17:45 openbsd 80126d5ff84a d4611817 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/02 15:21 openbsd 2f5495769435 d4611817 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/02 08:21 openbsd 2f5495769435 d4611817 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/01 15:00 openbsd 6cbdb9457802 d4611817 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/12/01 13:33 openbsd 6bf0f93af4a8 01c07bfe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/28 21:32 openbsd 88dc91f4cc14 d1b870e1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/28 10:17 openbsd 49d7e2aa733e e8331348 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/28 03:43 openbsd 49d7e2aa733e e8331348 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/28 01:39 openbsd 7de01a79e4ba e8331348 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/27 03:17 openbsd 6302f867eaf5 e8331348 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/25 15:17 openbsd db1d82999ce6 64219f15 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/25 01:01 openbsd 58395e5de74c 64219f15 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/24 20:38 openbsd 879ea5f6fdb7 bf6fe8fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/24 15:24 openbsd 879ea5f6fdb7 bf6fe8fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/24 07:06 openbsd 879ea5f6fdb7 4fb8ef37 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/23 09:57 openbsd d1bc7a39681f 4fb8ef37 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/23 04:07 openbsd d1bc7a39681f 4fb8ef37 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/22 09:35 openbsd 16f4e75c8e57 4fb8ef37 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/21 12:44 openbsd e35b8f0de8d7 52ed5c96 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/21 01:22 openbsd 664a2aa283c6 280ea308 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/19 20:50 openbsd 809b9478d116 82d7b894 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/19 06:48 openbsd 32bfe3a7a32f ef766cd7 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/18 23:21 openbsd ae8b598acb72 ef766cd7 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/18 11:10 openbsd ae8b598acb72 ef766cd7 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/16 09:42 openbsd 9c41abc406e3 f7988ea4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/16 02:18 openbsd 42d4ce758e42 f7988ea4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/14 21:17 openbsd 56163c0cd41e f7988ea4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/14 11:50 openbsd 83ff66b05700 07e030de .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/13 08:17 openbsd b192115449a5 07e030de .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/12 21:36 openbsd 4bd49954ab16 07e030de .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/12 06:27 openbsd f90c65410264 4e1406b4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/12 02:58 openbsd f90c65410264 4e1406b4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/11/11 15:30 openbsd 05de582f27ae 4e1406b4 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/09 05:44 openbsd 42468faed836 7e2882b3 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore SYZFAIL: tun: can't open device
2025/10/07 22:59 openbsd a66c1d641baa 7e2882b3 .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.