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

6 views
Skip to first unread message

syzbot

unread,
Oct 14, 2025, 3:23:33 AMOct 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

syzbot

unread,
Nov 7, 2025, 11:18:28 AM (3 days ago) Nov 7
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16829114580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
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
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136d5342580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d8305ca1c94/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8bc85383c07b/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d337081bce56/bzImage-f6e38ae6.xz
proc=3 req=2889 state=3 status=67 (errno 32: Broken pipe)
connection error: failed to recv *flatrpc.ExecutorMessageRawT: read tcp 127.0.0.1:44069->127.0.0.1:41286: read: connection reset by peer


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

syzbot

unread,
Nov 7, 2025, 11:34:33 AM (3 days ago) Nov 7
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15629114580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=3730c68ed0e9291dbcdb
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d23812580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed7568bc5bb4/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e343e0aaac77/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/089870f2a980/bzImage-cc5ec876.xz

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

2025/11/07 16:33:24 executed programs: 3489
2025/11/07 16:33:29 executed programs: 3608
2025/11/07 16:33:35 executed programs: 3720
2025/11/07 16:33:40 executed programs: 3804
2025/11/07 16:33:47 executed programs: 3860
proc=2 req=3236 state=3 status=67 (errno 32: Broken pipe)
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

Reply all
Reply to author
Forward
0 new messages