[v6.1] SYZFAIL: tun: ioctl(TUNSETIFF) failed (2)

6 views
Skip to first unread message

syzbot

unread,
Mar 23, 2025, 3:07:23 AM3/23/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=112f5c4c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1eebf09bc04ebd78
dashboard link: https://syzkaller.appspot.com/bug?extid=811fc6b31d1b24d050bc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/909838d42ed4/disk-344a0965.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1ee29eda8d53/vmlinux-344a0965.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f943effb4128/bzImage-344a0965.xz

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

SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: tun: ioctl(TUNSETIFF) failed
(errno 25: Inappropriate ioctl for device)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=3 req=23539 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,
Jan 12, 2026, 3:52:24 AMJan 12
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: bec0e10ee67e Linux 6.1.160
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1477199a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5cbd268406bf43
dashboard link: https://syzkaller.appspot.com/bug?extid=811fc6b31d1b24d050bc
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=1622a844580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eef10a13b127/disk-bec0e10e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75d8309ba559/vmlinux-bec0e10e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/59339d7672d2/bzImage-bec0e10e.xz
proc=1 req=2830 state=3 status=67 (errno 32: Broken pipe)
connection error: failed to recv *flatrpc.ExecutorMessageRawT: read tcp 127.0.0.1:43695->127.0.0.1:42462: 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.
Reply all
Reply to author
Forward
0 new messages