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

1 view
Skip to first unread message

syzbot

unread,
Jun 16, 2025, 10:50:32 AMJun 16
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15e30370580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=a80df67ec7ea18671d5e
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5819843271d0/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/113f268f936d/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/493dd7e2863f/bzImage-c2603c51.xz

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

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=3 req=11426 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

unread,
Sep 25, 2025, 4:03:20 AM (yesterday) Sep 25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages