[v6.1] SYZFAIL: tun: can't open /dev/net/tun (2)

3 views
Skip to first unread message

syzbot

unread,
Oct 14, 2025, 3:23:33 AM (3 days ago) Oct 14
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 882efbdd9d34 Linux 6.1.155
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15757892580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=2036e33bb2d401ccef8d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ace97ceaac60/disk-882efbdd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/88315d1cd2fa/vmlinux-882efbdd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5e607a61f425/Image-882efbdd.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2036e3...@syzkaller.appspotmail.com

SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=1 req=309 state=3 status=67 (errno 32: Broken pipe)


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages