[syzbot] [mm?] WARNING in unlink_anon_vmas (2)

syzbot
2026-01-18T07:30:25Z

Hello,

syzbot found the following issue on:

HEAD commit: b775e489bec7 Add linux-next specific files for 20260114
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15dbc444580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2dcf53f0a51185
dashboard link: https://syzkaller.appspot.com/bug?extid=c27fa543e10a45d4e149
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=17070522580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1683f99a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e077e7eafdc/disk-b775e489.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea69aef6ee56/vmlinux-b775e489.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b8b6986280d1/bzImage-b775e489.xz

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

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007f16655e5fa0 R14: 00007f16655e5fa0 R15: 0000000000000002
</TASK>
------------[ cut here ]------------
WARNING: mm/rmap.c:480 at unlink_anon_vmas+0x701/0x730 mm/rmap.c:480, CPU#0: syz.0.20/5987
Modules linked in:
CPU: 0 UID: 0 PID: 5987 Comm: syz.0.20 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:unlink_anon_vmas+0x701/0x730 mm/rmap.c:480
Code: ac ff 48 83 c4 40 5b 41 5c 41 5d 41 5e 41 5f 5d e9 84 df 56 09 cc e8 8e ed ac ff 90 0f 0b 90 e9 e2 f9 ff ff e8 80 ed ac ff 90 <0f> 0b 90 eb d3 48 c7 c1 10 ab c4 8f 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc900033676c0 EFLAGS: 00010293
RAX: ffffffff821460b0 RBX: dffffc0000000000 RCX: ffff88802a773c80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff8fc47af7 R09: 1ffffffff1f88f5e
R10: dffffc0000000000 R11: fffffbfff1f88f5f R12: 1ffff110062fbaa8
R13: ffff888027aad900 R14: ffff8880317dd510 R15: ffff8880317dd530
FS: 0000555592787500(0000) GS:ffff8881259ad000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f166526615a CR3: 000000002f0cc000 CR4: 00000000003526f0
Call Trace:
<TASK>
anon_vma_fork+0x4b9/0x500 mm/rmap.c:438
dup_mmap+0x954/0x1b80 mm/mmap.c:1790
dup_mm kernel/fork.c:1529 [inline]
copy_mm+0x13c/0x4b0 kernel/fork.c:1581
copy_process+0x1812/0x3ba0 kernel/fork.c:2218
kernel_clone+0x21e/0x820 kernel/fork.c:2648
__do_sys_clone3 kernel/fork.c:2950 [inline]
__se_sys_clone3+0x256/0x2d0 kernel/fork.c:2929
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f166538f749
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:00007ffe55f4df08 EFLAGS: 00000246 ORIG_RAX: 00000000000001b3
RAX: ffffffffffffffda RBX: 0000000000000058 RCX: 00007f166538f749
RDX: 00007ffe55f4df20 RSI: 0000000000000058 RDI: 00007ffe55f4df20
RBP: 00007ffe55f4e090 R08: 0000000000000000 R09: 0000000000000058
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007f16655e5fa0 R14: 00007f16655e5fa0 R15: 0000000000000002
</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 syzkaller@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