[v6.1] SYZFAIL: vendor_pkt_req write failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b67dc5c9ade9 Linux 6.1.118
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=150d1ac0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d16b871b055cdb66
dashboard link: https://syzkaller.appspot.com/bug?extid=e1b1c989f12b16e4dfc8
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/c65b9855ed80/disk-b67dc5c9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/34d402bfdd1c/vmlinux-b67dc5c9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dcaa1163f7f5/bzImage-b67dc5c9.xz

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

SYZFAIL: vendor_pkt_req write failed
(errno 77: File descriptor in bad state)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=5 req=1584 state=3 status=67 (errno 9: Bad file descriptor)


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.