From: Kees Cook <kees@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: syzbot <syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
luto@amacapital.net, syzkaller-bugs@googlegroups.com,
wad@chromium.org
Subject: Re: [syzbot] [io-uring?] WARNING in __secure_computing
Date: Thu, 19 Feb 2026 10:53:57 -0800 [thread overview]
Message-ID: <202602191048.395EE1E@keescook> (raw)
In-Reply-To: <c71fc714-25b2-4c56-b48a-6d9da1d40d60@kernel.dk>
On Wed, Feb 18, 2026 at 09:27:07AM -0700, Jens Axboe wrote:
> On 2/17/26 9:00 PM, syzbot wrote:
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13256722580000
> > [...]
> > WARNING: kernel/seccomp.c:1407 at __secure_computing+0x2ae/0x2e0 kernel/seccomp.c:1407, CPU#1: syz.0.17/6077
This is:
/* Surviving SECCOMP_RET_KILL_* must be proactively impossible. */
case SECCOMP_MODE_DEAD:
WARN_ON_ONCE(1);
do_exit(SIGKILL);
return -1;
It's nice to see we caught an impossible state! :) Now we just need to
figure out what the repro is doing.
> Not io_uring, no seccomp label that I can find...
Why do you say this? The reproducer sets up io_uring and then calls
seccomp:
int main(void)
{
...
// io_uring_enter arguments: [
// fd: fd_io_uring (resource)
// to_submit: int32 = 0x847ba (4 bytes)
// min_complete: int32 = 0x0 (4 bytes)
// flags: io_uring_enter_flags = 0xe (8 bytes)
// sigmask: nil
// size: len = 0x0 (8 bytes)
// ]
syscall(
__NR_io_uring_enter, /*fd=*/r[1], /*to_submit=*/0x847ba,
/*min_complete=*/0,
/*flags=IORING_ENTER_EXT_ARG|IORING_ENTER_SQ_WAIT|IORING_ENTER_SQ_WAKEUP*/
0xeul, /*sigmask=*/0ul, /*size=*/0ul);
// seccomp$SECCOMP_SET_MODE_FILTER_LISTENER arguments: [
// op: const = 0x1 (8 bytes)
// flags: seccomp_flags_listener = 0x0 (8 bytes)
// arg: ptr[in, sock_fprog] {
// sock_fprog {
// len: len = 0x1 (2 bytes)
// pad = 0x0 (6 bytes)
// filter: ptr[in, array[sock_filter]] {
// array[sock_filter] {
// sock_filter {
// code: int16 = 0x6 (2 bytes)
// jt: int8 = 0xff (1 bytes)
// jf: int8 = 0x1 (1 bytes)
// k: int32 = 0x3fff0000 (4 bytes)
// }
// }
// }
// }
// }
// ]
// returns fd_seccomp
NONFAILING(*(uint16_t*)0x200000000240 = 1);
NONFAILING(*(uint64_t*)0x200000000248 = 0x2000000003c0);
NONFAILING(*(uint16_t*)0x2000000003c0 = 6);
NONFAILING(*(uint8_t*)0x2000000003c2 = -1);
NONFAILING(*(uint8_t*)0x2000000003c3 = 1);
NONFAILING(*(uint32_t*)0x2000000003c4 = 0x3fff0000);
syscall(__NR_seccomp, /*op=*/1ul, /*flags=*/0ul, /*arg=*/0x200000000240ul);
return 0;
}
So something has gone weird here, I assume related to seccomp listener
vs io_uring and process death.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2026-02-19 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 4:00 [syzbot] [io-uring?] WARNING in __secure_computing syzbot
2026-02-18 16:27 ` Jens Axboe
2026-02-19 18:53 ` Kees Cook [this message]
2026-02-20 13:44 ` Jens Axboe
2026-02-23 19:15 ` Jens Axboe
2026-02-24 0:08 ` Kees Cook
2026-04-04 14:20 ` Oleg Nesterov
2026-04-04 14:41 ` [syzbot] [kernel] " syzbot
2026-04-05 14:20 ` [syzbot] [io-uring?] " Oleg Nesterov
2026-04-05 14:40 ` [syzbot] [kernel] " syzbot
2026-04-05 15:10 ` Oleg Nesterov
2026-04-05 15:29 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202602191048.395EE1E@keescook \
--to=kees@kernel.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wad@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.