[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAgD-7-Z+xbXwtvA9n9X2YE-B9f2bHFtyQxkX1uL+Yqd5zRuQ@mail.gmail.com>
Date: Wed, 28 Aug 2024 16:34:39 -0700
From: Xingyu Li <xli399@....edu>
To: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, dsahern@...nel.org, j.granados@...sung.com,
linux@...ssschuh.net, judyhsiao@...omium.org, James.Z.Li@...l.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Yu Hao <yhao016@....edu>
Subject: BUG: corrupted list in neigh_destroy
Hi,
We found a bug in Linux 6.10 using syzkaller. It is possibly a
corrupted list bug.
The bug report is as follows, but unfortunately there is no generated
syzkaller reproducer.
Bug report:
list_del corruption, ffff88802cfc0d80->next is NULL
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:53!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 PID: 4497 Comm: kworker/0:3 Not tainted 6.10.0 #13
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Workqueue: events_power_efficient neigh_periodic_work
RIP: 0010:__list_del_entry_valid_or_report+0xc3/0x120 lib/list_debug.c:52
Code: 08 48 89 df e8 4e 01 96 fd 48 8b 13 4c 39 fa 75 62 b0 01 5b 41
5c 41 5e 41 5f c3 48 c7 c7 60 5a a9 8b 4c 89 fe e8 dd ff 96 06 <0f> 0b
48 c7 c7 c0 5a a9 8b 4c 89 fe e8 cc ff 96 06 0f 0b 48 c7 c7
RSP: 0018:ffffc90002ce7978 EFLAGS: 00010046
RAX: 0000000000000033 RBX: 0000000000000000 RCX: 31a71fdaa0dd1600
RDX: 0000000000000000 RSI: 0000000080000202 RDI: 0000000000000000
RBP: ffffc90002ce7ac8 R08: ffffffff8172e30c R09: 1ffff9200059ced0
R10: dffffc0000000000 R11: fffff5200059ced1 R12: dffffc0000000000
R13: ffff88802cfc0d80 R14: 0000000000000000 R15: ffff88802cfc0d80
FS: 0000000000000000(0000) GS:ffff888063a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055dc1a4cee78 CR3: 000000000d932000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_move_tail include/linux/list.h:310 [inline]
ref_tracker_free+0x191/0x7b0 lib/ref_tracker.c:262
netdev_tracker_free include/linux/netdevice.h:4058 [inline]
netdev_put include/linux/netdevice.h:4075 [inline]
neigh_destroy+0x317/0x570 net/core/neighbour.c:914
neigh_periodic_work+0x3c6/0xd40 net/core/neighbour.c:1007
process_one_work kernel/workqueue.c:3248 [inline]
process_scheduled_works+0x977/0x1410 kernel/workqueue.c:3329
worker_thread+0xaa0/0x1020 kernel/workqueue.c:3409
kthread+0x2eb/0x380 kernel/kthread.c:389
ret_from_fork+0x49/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0xc3/0x120 lib/list_debug.c:52
Code: 08 48 89 df e8 4e 01 96 fd 48 8b 13 4c 39 fa 75 62 b0 01 5b 41
5c 41 5e 41 5f c3 48 c7 c7 60 5a a9 8b 4c 89 fe e8 dd ff 96 06 <0f> 0b
48 c7 c7 c0 5a a9 8b 4c 89 fe e8 cc ff 96 06 0f 0b 48 c7 c7
RSP: 0018:ffffc90002ce7978 EFLAGS: 00010046
RAX: 0000000000000033 RBX: 0000000000000000 RCX: 31a71fdaa0dd1600
RDX: 0000000000000000 RSI: 0000000080000202 RDI: 0000000000000000
RBP: ffffc90002ce7ac8 R08: ffffffff8172e30c R09: 1ffff9200059ced0
R10: dffffc0000000000 R11: fffff5200059ced1 R12: dffffc0000000000
R13: ffff88802cfc0d80 R14: 0000000000000000 R15: ffff88802cfc0d80
FS: 0000000000000000(0000) GS:ffff888063a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055dc1a4cee78 CR3: 000000000d932000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
--
Yours sincerely,
Xingyu
Powered by blists - more mailing lists