[v6.6] SYZFAIL: open(/proc/self/ns/net) failed

syzbot

unread,

Sep 2, 2026, 7:13:57 PMSep 2

to syzkaller...@googlegroups.com

Hello,

syzbot found the following issue on:

HEAD commit: 8b73de7da85f Linux 6.6.156
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=125290f9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=36b7405af75229890a2d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d7e87682fef0/disk-8b73de7d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/096830afc063/vmlinux-8b73de7d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/89c175e4560d/bzImage-8b73de7d.xz

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

SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: open(/proc/self/ns/net) failed
(errno 2: No such file or directory)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=5 req=822 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,

Sep 3, 2026, 7:04:40 AMSep 3

to syzkaller...@googlegroups.com

Hello,

syzbot found the following issue on:

HEAD commit: cf82dcca9634 Linux 6.1.187
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11ffc125580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=3cf5c5d0a412f48b2253

compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/97e1e40b968b/disk-cf82dcca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cfec27562c15/vmlinux-cf82dcca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4c7cd066c46d/bzImage-cf82dcca.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+3cf5c5...@syzkaller.appspotmail.com

proc=4 req=1594 state=3 status=67 (errno 32: Broken pipe)

syzbot

unread,

Sep 5, 2026, 11:23:37 PMSep 5

to syzkaller...@googlegroups.com

syzbot has found a reproducer for the following issue on:

HEAD commit: cf82dcca9634 Linux 6.1.187
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=11f59125580000

kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=3cf5c5d0a412f48b2253
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c7acf9580000

proc=1 req=19 state=3 status=67 (errno 9: Bad file descriptor)
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF

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