linux-kernel - [syzbot] [kernel?] kernel BUG in qlist_free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <68c6c3b1.050a0220.2ff435.0382.GAE@google.com>
Date: Sun, 14 Sep 2025 06:31:29 -0700
From: syzbot <syzbot+8715dd783e9b0bef43b1@...kaller.appspotmail.com>
To: bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com, 
	linux-kernel@...r.kernel.org, luto@...nel.org, mingo@...hat.com, 
	peterz@...radead.org, syzkaller-bugs@...glegroups.com, tglx@...utronix.de, 
	x86@...nel.org
Subject: [syzbot] [kernel?] kernel BUG in qlist_free_all (2)

Hello,

syzbot found the following issue on:

HEAD commit:    9dd1835ecda5 Merge tag 'dma-mapping-6.17-2025-09-09' of gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1663cb12580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e0bea6c0b97a2002
dashboard link: https://syzkaller.appspot.com/bug?extid=8715dd783e9b0bef43b1
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3bd34622db2f/disk-9dd1835e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/673ef735e573/vmlinux-9dd1835e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eb16aa1b210d/bzImage-9dd1835e.xz

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

------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 456 Comm: syz-executor Tainted: G     U              syzkaller #0 PREEMPT(full) 
Tainted: [U]=USER
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:__phys_addr+0xfa/0x180 arch/x86/mm/physaddr.c:28
Code: 48 d3 e8 48 89 c3 48 89 c6 e8 82 80 4e 00 48 85 db 75 11 e8 08 85 4e 00 48 89 e8 5b 5d 41 5c c3 cc cc cc cc e8 f7 84 4e 00 90 <0f> 0b e8 ef 84 4e 00 48 c7 c0 10 b0 3a 8e 48 ba 00 00 00 00 00 fc
RSP: 0018:ffffc9000c6f74b0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 3fffff890062e864 RCX: ffffffff816c85f3
RDX: ffff8880255bda00 RSI: ffffffff816c8679 RDI: 0000000000000006
RBP: 400077088062e864 R08: 0000000000000006 R09: 3fffff890062e864
R10: 400077088062e864 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc9000c6f7508 R15: ffff888022aa0001
FS:  0000555589044500(0000) GS:ffff8881247bd000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1fea5056c0 CR3: 0000000076f3e000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 virt_to_folio include/linux/mm.h:1180 [inline]
 virt_to_slab mm/slab.h:187 [inline]
 qlink_to_cache mm/kasan/quarantine.c:131 [inline]
 qlist_free_all+0x65/0x120 mm/kasan/quarantine.c:176
 kasan_quarantine_reduce+0x195/0x1e0 mm/kasan/quarantine.c:286
 __kasan_slab_alloc+0x69/0x90 mm/kasan/common.c:340
 kasan_slab_alloc include/linux/kasan.h:250 [inline]
 slab_post_alloc_hook mm/slub.c:4191 [inline]
 slab_alloc_node mm/slub.c:4240 [inline]
 kmem_cache_alloc_noprof+0x1cb/0x3b0 mm/slub.c:4247
 ptlock_alloc+0x1f/0x70 mm/memory.c:7161
 ptlock_init include/linux/mm.h:2953 [inline]
 pagetable_pte_ctor include/linux/mm.h:3002 [inline]
 __pte_alloc_one_noprof include/asm-generic/pgalloc.h:78 [inline]
 pte_alloc_one+0x82/0x3a0 arch/x86/mm/pgtable.c:18
 __pte_alloc+0x6d/0x3c0 mm/memory.c:452
 copy_pte_range mm/memory.c:1107 [inline]
 copy_pmd_range mm/memory.c:1261 [inline]
 copy_pud_range mm/memory.c:1298 [inline]
 copy_p4d_range mm/memory.c:1322 [inline]
 copy_page_range+0x3b83/0x5c80 mm/memory.c:1410
 dup_mmap+0xe88/0x21d0 mm/mmap.c:1834
 dup_mm kernel/fork.c:1485 [inline]
 copy_mm kernel/fork.c:1537 [inline]
 copy_process+0x4081/0x7690 kernel/fork.c:2175
 kernel_clone+0xfc/0x930 kernel/fork.c:2605
 __do_sys_clone+0xce/0x120 kernel/fork.c:2748
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1fe9785413
Code: 1f 84 00 00 00 00 00 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00
RSP: 002b:00007ffd86810ba8 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1fe9785413
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001
R10: 00005555890447d0 R11: 0000000000000246 R12: 0000000000000000
R13: 00000000000927c0 R14: 0000000000164bcc R15: 00007ffd86810d40
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__phys_addr+0xfa/0x180 arch/x86/mm/physaddr.c:28
Code: 48 d3 e8 48 89 c3 48 89 c6 e8 82 80 4e 00 48 85 db 75 11 e8 08 85 4e 00 48 89 e8 5b 5d 41 5c c3 cc cc cc cc e8 f7 84 4e 00 90 <0f> 0b e8 ef 84 4e 00 48 c7 c0 10 b0 3a 8e 48 ba 00 00 00 00 00 fc
RSP: 0018:ffffc9000c6f74b0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 3fffff890062e864 RCX: ffffffff816c85f3
RDX: ffff8880255bda00 RSI: ffffffff816c8679 RDI: 0000000000000006
RBP: 400077088062e864 R08: 0000000000000006 R09: 3fffff890062e864
R10: 400077088062e864 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc9000c6f7508 R15: ffff888022aa0001
FS:  0000555589044500(0000) GS:ffff8881247bd000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000800000 CR3: 0000000076f3e000 CR4: 00000000003526f0


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