[syzbot] [kernel?] INFO: trying to register non-static key in skb_dequeue (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5d50cf9f7cf2 Add linux-next specific files for 20250903
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12fade62580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d2429dff5531d80
dashboard link: https://syzkaller.appspot.com/bug?extid=bb185b018a51f8d91fd2
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b9a312580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16819e62580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/779c4c33db6a/disk-5d50cf9f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f80abaffa076/vmlinux-5d50cf9f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/65fcb4766d7b/bzImage-5d50cf9f.xz

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

RBP: 00007ffc4d7c4a10 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fc6a7fc5fa0 R14: 00007fc6a7fc5fa0 R15: 0000000000000003
</TASK>
INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 0 UID: 0 PID: 6073 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
<TASK>
dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
assign_lock_key+0x133/0x150 kernel/locking/lockdep.c:984
register_lock_class+0x105/0x320 kernel/locking/lockdep.c:1299
__lock_acquire+0x99/0xd20 kernel/locking/lockdep.c:5112
lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162
skb_dequeue+0x2e/0x150 net/core/skbuff.c:3897
audit_buffer_free kernel/audit.c:1820 [inline]
audit_buffer_alloc kernel/audit.c:1850 [inline]
audit_log_start+0x47b/0xa90 kernel/audit.c:1954
audit_seccomp+0x64/0x190 kernel/auditsc.c:2976
seccomp_log kernel/seccomp.c:1048 [inline]
__seccomp_filter+0x9a0/0x1a30 kernel/seccomp.c:1344
syscall_trace_enter+0xaa/0x160 kernel/entry/syscall-common.c:44
syscall_enter_from_user_mode_work include/linux/entry-common.h:95 [inline]
syscall_enter_from_user_mode include/linux/entry-common.h:125 [inline]
do_syscall_64+0xd3/0xfa0 arch/x86/entry/syscall_64.c:90
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc6a7d8ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc4d7c49b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007fc6a7fc5fa0 RCX: 00007fc6a7d8ebe9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffffffffff
RBP: 00007ffc4d7c4a10 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fc6a7fc5fa0 R14: 00007fc6a7fc5fa0 R15: 0000000000000003
</TASK>
audit: audit_lost=1 audit_rate_limit=0 audit_backlog_limit=64
audit: out of memory in audit_log_start


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

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]

syzbot has bisected this issue to:

commit eb59d494eebd4c5414728a35cdea6a0ba78ff26e
Author: Casey Schaufler <ca...@schaufler-ca.com>
Date: Sat Aug 16 17:28:58 2025 +0000

audit: add record for multiple task security contexts

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1199fe62580000
start commit: 5d50cf9f7cf2 Add linux-next specific files for 20250903
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1399fe62580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1599fe62580000

kernel config: https://syzkaller.appspot.com/x/.config?x=7d2429dff5531d80
dashboard link: https://syzkaller.appspot.com/bug?extid=bb185b018a51f8d91fd2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b9a312580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16819e62580000

Reported-by: syzbot+bb185b...@syzkaller.appspotmail.com
Fixes: eb59d494eebd ("audit: add record for multiple task security contexts")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

[Paul Moore]

The timing on this is amusing, I got the sysbot report just as I
merged a fix for this provided by Eric Dumazet :)

https://lore.kernel.org/audit/20250904072537.2...@google.com

The commit has the appropriate syzbot tags so this should close out
automatically.

--
paul-moore.com