[v5.15] SYZFAIL: tun read failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d0fc081c6241 Linux 5.15.143
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14c7291ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ffd22c928742e176
dashboard link: https://syzkaller.appspot.com/bug?extid=de435d5aa6370353cef3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14190e76e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c315e9d55a2d/disk-d0fc081c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0543a2c39d86/vmlinux-d0fc081c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b6820cee1703/bzImage-d0fc081c.xz

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

2023/12/20 12:40:34 [FATAL] executor failed 11 times: executor 0: exit status 67 err exit status 67
SYZFAIL: tun read failed
(errno 9: Bad file descriptor)
SYZFAIL: child failed
(errno 0: Success)
loop exited with status 67
exit status 67

SYZFAIL: tun read failed
(errno 9: Bad file descriptor)
SYZFAIL: child failed
(errno 0: Success)
loop exited with status 67
exit status 67


---
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.

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