[syzbot] [bpf?] WARNING: kmalloc bug in bpf_prog_alloc_no_stats

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0c1c7a6a83fe Add linux-next specific files for 20251117
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12c86692580000
kernel config: https://syzkaller.appspot.com/x/.config?x=78555cc0f7025c00
dashboard link: https://syzkaller.appspot.com/bug?extid=d4264133b3e51212ea30
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/30639e6c3546/disk-0c1c7a6a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/88fdcd914c22/vmlinux-0c1c7a6a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/087028e72d0f/bzImage-0c1c7a6a.xz

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

------------[ cut here ]------------
Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to gfp: 0xdc0 (GFP_KERNEL|__GFP_ZERO). Fix your code!
WARNING: mm/vmalloc.c:3938 at vmalloc_fix_flags+0x9c/0xe0 mm/vmalloc.c:3937, CPU#1: syz-executor/6076
Modules linked in:
CPU: 1 UID: 0 PID: 6076 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:vmalloc_fix_flags+0x9c/0xe0 mm/vmalloc.c:3937
Code: 81 e6 1f 52 ee ff 89 74 24 30 81 e3 e0 ad 11 00 89 5c 24 20 90 48 c7 c7 a0 db 96 8b 4c 89 fa 89 d9 4d 89 f0 e8 85 8d 6c ff 90 <0f> 0b 90 90 8b 44 24 20 48 c7 04 24 0e 36 e0 45 4b c7 04 2c 00 00
RSP: 0018:ffffc900043cfb00 EFLAGS: 00010246
RAX: a51e1d8e991b0100 RBX: 0000000000000dc0 RCX: ffff888031d2bd00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffc900043cfb98 R08: ffffc900043cf827 R09: 1ffff92000879f04
R10: dffffc0000000000 R11: fffff52000879f05 R12: 1ffff92000879f60
R13: dffffc0000000000 R14: ffffc900043cfb20 R15: ffffc900043cfb30
FS: 0000555589c86500(0000) GS:ffff888125b74000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa89645c470 CR3: 0000000079642000 CR4: 00000000003526f0
Call Trace:
<TASK>
__vmalloc_noprof+0xf2/0x120 mm/vmalloc.c:4124
bpf_prog_alloc_no_stats+0x4a/0x4d0 kernel/bpf/core.c:106
bpf_prog_alloc+0x3c/0x1a0 kernel/bpf/core.c:153
bpf_prog_create_from_user+0xa7/0x440 net/core/filter.c:1443
seccomp_prepare_filter kernel/seccomp.c:701 [inline]
seccomp_prepare_user_filter kernel/seccomp.c:738 [inline]
seccomp_set_mode_filter kernel/seccomp.c:1990 [inline]
do_seccomp+0x7b1/0xd90 kernel/seccomp.c:2110
__do_sys_prctl kernel/sys.c:2610 [inline]
__se_sys_prctl+0xc3c/0x1830 kernel/sys.c:2518
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa896590b0d
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 18 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 9d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 1b 48 8b 54 24 18 64 48 2b 14 25 28 00 00 00
RSP: 002b:00007ffe0659e8d0 EFLAGS: 00000246 ORIG_RAX: 000000000000009d
RAX: ffffffffffffffda RBX: 00007fa89662cf80 RCX: 00007fa896590b0d
RDX: 00007ffe0659e930 RSI: 0000000000000002 RDI: 0000000000000016
RBP: 00007ffe0659e940 R08: 0000000000000006 R09: 0000000000000071
R10: 0000000000000071 R11: 0000000000000246 R12: 000000000000006d
R13: 00007ffe0659ed68 R14: 00007ffe0659efe8 R15: 0000000000000000
</TASK>


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