public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com>,
	io-uring@vger.kernel.org, kees@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: Wed, 18 Feb 2026 09:27:07 -0700	[thread overview]
Message-ID: <c71fc714-25b2-4c56-b48a-6d9da1d40d60@kernel.dk> (raw)
In-Reply-To: <69953966.a70a0220.2c38d7.0111.GAE@google.com>

On 2/17/26 9:00 PM, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    2961f841b025 Merge tag 'turbostat-2026.02.14' of git://git..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1721315a580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=e2f061f80b102378
> dashboard link: https://syzkaller.appspot.com/bug?extid=0a4c46806941297fecb9
> compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=142edb3a580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13256722580000
> 
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-2961f841.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/4f9939f81465/vmlinux-2961f841.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/3f9babe832cd/bzImage-2961f841.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+0a4c46806941297fecb9@syzkaller.appspotmail.com
> 
> ------------[ cut here ]------------
> 1
> WARNING: kernel/seccomp.c:1407 at __secure_computing+0x2ae/0x2e0 kernel/seccomp.c:1407, CPU#1: syz.0.17/6077
> Modules linked in:
> CPU: 1 UID: 0 PID: 6077 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> RIP: 0010:__secure_computing+0x2ae/0x2e0 kernel/seccomp.c:1407
> Code: 00 e8 96 52 fe ff e8 31 27 ff ff e8 fc 68 6b 00 bf 09 00 00 00 e8 82 f0 be ff e8 3d 79 6b 00 e9 06 fe ff ff e8 13 27 ff ff 90 <0f> 0b 90 e8 da 68 6b 00 bf 09 00 00 00 e8 60 f0 be ff e8 fb 26 ff
> RSP: 0018:ffffc9000413fed0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffffc9000413ff48 RCX: ffffffff82097151
> RDX: ffff888035c04900 RSI: ffffffff8209730d RDI: ffff888035c04900
> RBP: 0000000000000003 R08: 0000000000000005 R09: 0000000000000003
> R10: 0000000000000003 R11: 0000000000000000 R12: 00000000000001b4
> R13: 00000000000001b4 R14: ffff888035c04900 R15: 0000000000000001
> FS:  0000555575c2e500(0000) GS:ffff8880d644a000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f20e8a71fc0 CR3: 00000000373f5000 CR4: 0000000000352ef0
> Call Trace:
>  <TASK>
>  syscall_trace_enter include/linux/entry-common.h:112 [inline]
>  syscall_enter_from_user_mode_work include/linux/entry-common.h:156 [inline]
>  syscall_enter_from_user_mode include/linux/entry-common.h:187 [inline]
>  do_syscall_64+0x568/0xf80 arch/x86/entry/syscall_64.c:90
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f20e8b9c629
> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffd25984108 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
> RAX: ffffffffffffffda RBX: 00007ffd259841f0 RCX: 00007f20e8b9c629
> RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
> RBP: 000000000000f6e1 R08: 0000000000000001 R09: 0000000000000000
> R10: 0000001b2d120000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007f20e8e15fac R14: 00007f20e8e15fa8 R15: 00007f20e8e15fa0
>  </TASK>

Not io_uring, no seccomp label that I can find...

#syz set subsystems: kernel

-- 
Jens Axboe


      reply	other threads:[~2026-02-18 16:27 UTC|newest]

Thread overview: 2+ 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 [this message]

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=c71fc714-25b2-4c56-b48a-6d9da1d40d60@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kees@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox