[v6.1] SYZFAIL: ebtable: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c1cec4dad96b Linux 6.1.102
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126fede3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ecafd35d4eb83494
dashboard link: https://syzkaller.appspot.com/bug?extid=f669518b7d0ff9a91e77
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b1eac80ef090/disk-c1cec4da.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3ea071167e94/vmlinux-c1cec4da.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47179f6541c0/Image-c1cec4da.gz.xz

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

SYZFAIL: ebtable: 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: 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=4 req=470 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]

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