syzbot


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: 6d04h, last: 1h17m
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 1542d 1542d 0/3 auto-closed as invalid on 2021/10/22 18:00
openbsd SYZFAIL: tun: can't open device (6) -1 31 72d 113d 0/3 auto-obsoleted due to no activity on 2025/09/21 09:12
openbsd SYZFAIL: tun: can't open device (3) -1 86 1368d 1368d 0/3 closed as invalid on 2022/01/15 08:41
openbsd SYZFAIL: tun: can't open device (5) -1 82 219d 235d 0/3 auto-obsoleted due to no activity on 2025/04/27 11:29
openbsd SYZFAIL: tun: can't open device -1 syz 4 1684d 1684d 3/3 fixed on 2021/03/10 05:59
openbsd SYZFAIL: tun: can't open device (4) -1 8 358d 460d 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/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap3 (errno 16: Device busy)
SYZFAIL: repeatedly failed to execute the program
proc=3 req=4 state=1 status=67 (errno 35: Resource temporarily unavailable)

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/14 02:11 openbsd 0ee618c489a8 b6605ba8 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/14 01:40 openbsd 0ee618c489a8 b6605ba8 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/13 14:13 openbsd 105f350ce01a b6605ba8 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/11 18:17 openbsd 0f168beaa75c ff1712fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/11 03:11 openbsd ba3be980ae71 ff1712fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/10 23:15 openbsd 2d7977329ed5 ff1712fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/10 22:50 openbsd 2d7977329ed5 ff1712fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/10 11:20 openbsd f02b280c025a ff1712fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/10 10:06 openbsd f02b280c025a ff1712fe .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main SYZFAIL: tun: can't open device
2025/10/09 22:04 openbsd d147d1032c49 7e2882b3 .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/08 09:28 openbsd a66c1d641baa 7e2882b3 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main 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.