Hello,
syzbot found the following issue on:
HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1037acc6580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link:
https://syzkaller.appspot.com/bug?extid=0d3d0d568286317f6db9
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/d420eb944682/disk-fb28aa72.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/affae450ab23/vmlinux-fb28aa72.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/b9e6919ed519/Image-fb28aa72.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+0d3d0d...@syzkaller.appspotmail.com
names_cache 15134KB 15499KB
net_namespace 56KB 56KB
lsm_inode_cache 1724KB 1729KB
lsm_file_cache 328KB 496KB
key_jar 15KB 15KB
uts_namespace 15KB 15KB
nsproxy 7KB 7KB
vm_area_struct 746KB 918KB
fs_cache 45KB 84KB
files_cache 253KB 334KB
signal_cache 580KB 1366KB
sighand_cache 601KB 601KB
task_struct 2359KB 3136KB
cred_jar 185KB 322KB
anon_vma_chain 347KB 429KB
anon_vma 91KB 119KB
pid 93KB 202KB
Acpi-Operand 100KB 110KB
Acpi-ParseExt 11KB 11KB
Acpi-Parse 19KB 19KB
Acpi-State 39KB 59KB
Acpi-Namespace 12KB 12KB
numa_policy 3KB 3KB
trace_event_file 472KB 472KB
ftrace_event_field 845KB 845KB
pool_workqueue 192KB 192KB
maple_node 7871KB 9112KB
task_group 30KB 30KB
mm_struct 258KB 567KB
vmap_area 159KB 275KB
debug_objects_cache 1824KB 1824KB
page->ptl 141KB 224KB
kmalloc-cg-8k 1216KB 1216KB
kmalloc-cg-4k 14384KB 14656KB
kmalloc-cg-2k 9056KB 9056KB
kmalloc-cg-1k 2596KB 2720KB
kmalloc-cg-512 1953KB 2112KB
kmalloc-cg-256 192KB 192KB
kmalloc-cg-128 499KB 572KB
kmalloc-8k 7456KB 7744KB
kmalloc-4k 83704KB 83704KB
kmalloc-2k 19452KB 20524KB
kmalloc-1k 25408KB 25408KB
kmalloc-512 44352KB 44352KB
kmalloc-256 5648KB 5648KB
kmalloc-128 16000KB 16000KB
kmem_cache_node 132KB 132KB
kmem_cache 196KB 196KB
Out of memory and no killable processes...
Kernel panic - not syncing: System is deadlocked on memory
CPU: 1 PID: 3901 Comm: kworker/1:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
Workqueue: mld mld_dad_work
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack+0x30/0x40 lib/dump_stack.c:88
dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
panic+0x2f8/0x7ac kernel/panic.c:339
out_of_memory+0xee4/0xf70 mm/oom_kill.c:1181
__alloc_pages_may_oom mm/page_alloc.c:4525 [inline]
__alloc_pages_slowpath+0x1684/0x1e1c mm/page_alloc.c:5333
__alloc_pages+0x338/0x544 mm/page_alloc.c:5671
alloc_pages+0x434/0x6fc mm/mempolicy.c:-1
alloc_slab_page+0x78/0x144 mm/slub.c:1799
allocate_slab mm/slub.c:1952 [inline]
new_slab+0x1f4/0x2d8 mm/slub.c:1997
___slab_alloc+0x890/0xe90 mm/slub.c:3154
__slab_alloc+0x74/0xd0 mm/slub.c:3240
slab_alloc_node mm/slub.c:3325 [inline]
__kmem_cache_alloc_node+0x298/0x318 mm/slub.c:3398
__do_kmalloc_node mm/slab_common.c:935 [inline]
__kmalloc_node_track_caller+0xb8/0x174 mm/slab_common.c:956
kmalloc_reserve net/core/skbuff.c:446 [inline]
__alloc_skb+0x260/0x728 net/core/skbuff.c:515
alloc_skb include/linux/skbuff.h:1303 [inline]
mld_newpack+0x11c/0xa30 net/ipv6/mcast.c:1773
add_grhead net/ipv6/mcast.c:1884 [inline]
add_grec+0x1130/0x15b0 net/ipv6/mcast.c:2023
mld_send_initial_cr+0x168/0x2fc net/ipv6/mcast.c:2268
mld_dad_work+0x40/0x1d8 net/ipv6/mcast.c:2294
process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292
worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439
kthread+0x254/0x2e0 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x0a0000,000f0097,a65bfea7
Memory Limit: none
Rebooting in 86400 seconds..
---
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