Hello,
syzbot found the following issue on:
HEAD commit: a1153c0deb44 Linux 6.6.147
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16188c9e580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f0bc3d90c30838b5
dashboard link:
https://syzkaller.appspot.com/bug?extid=304ce94b7efa3a6313d4
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/9f646bfa1b52/disk-a1153c0d.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/a2aec2e8f0fd/vmlinux-a1153c0d.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a7abe1f87405/bzImage-a1153c0d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+304ce9...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 13961 at mm/page_alloc.c:4477 __alloc_pages+0x2e4/0x460 mm/page_alloc.c:4477
Modules linked in:
CPU: 0 PID: 13961 Comm: syz.0.2230 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__alloc_pages+0x2e4/0x460 mm/page_alloc.c:4477
Code: 0c 25 28 00 00 00 48 3b 8c 24 a0 00 00 00 0f 85 9f 00 00 00 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 c6 05 92 1b a3 0c 01 <0f> 0b eb a4 a9 00 00 08 00 8b 74 24 0c 75 3e 44 89 f1 81 e1 7f ff
RSP: 0018:ffffc9000d12fa20 EFLAGS: 00010246
RAX: ffffc9000d12fa00 RBX: 1ffff92001a25f48 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc9000d12fa88
RBP: ffffc9000d12fb10 R08: ffffc9000d12fa87 R09: 0000000000000000
R10: ffffc9000d12fa60 R11: fffff52001a25f51 R12: 0000000000000013
R13: 0000000000000000 R14: 0000000000040cc0 R15: dffffc0000000000
FS: 00007f1fa66ad6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3fdb87 CR3: 000000002c370000 CR4: 00000000003506f0
Call Trace:
<TASK>
__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]
__kmalloc_large_node+0x8c/0x1f0 mm/slab_common.c:1148
__do_kmalloc_node mm/slab_common.c:995 [inline]
__kmalloc_node_track_caller+0x110/0x230 mm/slab_common.c:1027
memdup_user_nul+0x2c/0xf0 mm/util.c:284
bitmap_parse_user+0x23/0x70 lib/bitmap.c:464
cpumask_parse_user include/linux/cpumask.h:777 [inline]
write_irq_affinity kernel/irq/proc.c:153 [inline]
irq_affinity_proc_write+0x13c/0x230 kernel/irq/proc.c:182
pde_write fs/proc/inode.c:340 [inline]
proc_reg_write+0x1e4/0x2d0 fs/proc/inode.c:352
vfs_write+0x299/0x9a0 fs/read_write.c:582
ksys_write+0x151/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f1fa579e019
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:00007f1fa66ad028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f1fa5a25fa0 RCX: 00007f1fa579e019
RDX: 00000000fffffdd4 RSI: 0000200000000340 RDI: 0000000000000003
RBP: 00007f1fa583500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1fa5a26038 R14: 00007f1fa5a25fa0 R15: 00007ffdfc26aa68
</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