From: sanan.hasanou@gmail.com
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com
Subject: general protection fault in netdev_unregister_kobject
Date: Fri, 26 Jun 2026 14:25:53 -0700 (PDT) [thread overview]
Message-ID: <6a3eee61.0ca26d91.74bfa.10cf@mx.google.com> (raw)
Good day, dear maintainers,
We found a bug using a modified version of syzkaller.
Kernel Branch: 7.0-rc1
Kernel Config: <https://drive.google.com/open?id=1R0DVns3qzvptjvc0SPl0ylIGDOw-Js_9>
Reproducer: <https://drive.google.com/open?id=1RU45wvk731QPN0fF3-Gh8mpSkXgQXQrF>
Thank you!
Best regards,
Sanan Hasanov
Oops: general protection fault, probably for non-canonical address 0xdffffc000000000b: 0000 [#1] SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000058-0x000000000000005f]
CPU: 1 UID: 0 PID: 246588 Comm: kbnepd bnep0 Tainted: G L 7.0.0-rc1 #1 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del+0x4c/0xc0 lib/klist.c:230
Code: f5 49 89 dd 49 c1 ed 03 43 80 7c 3d 00 00 74 08 48 89 df e8 96 39 9e f5 4c 8b 33 49 83 e6 fe 49 8d 7e 58 48 89 f8 48 c1 e8 03 <42> 80 3c 38 00 74 05 e8 78 39 9e f5 4d 8b 66 58 4c 89 f7 e8 8c 16
RSP: 0018:ffffc90004d3f7e8 EFLAGS: 00010212
RAX: 000000000000000b RBX: ffff88804d043460 RCX: ffff8880243b9d00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000058
RBP: ffffc90004d3f810 R08: ffff888037d5ac33 R09: 1ffff11006fab586
R10: dffffc0000000000 R11: ffffed1006fab587 R12: ffff888050c12618
R13: 1ffff11009a0868c R14: 0000000000000000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880d9cdb000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5033991f2c CR3: 000000004fa9b000 CR4: 00000000000006f0
Call Trace:
<TASK>
device_del+0x2c2/0xce0 drivers/base/core.c:3855
netdev_unregister_kobject+0x262/0x380 net/core/net-sysfs.c:2329
unregister_netdevice_many_notify+0x1ae2/0x1f40 net/core/dev.c:12436
unregister_netdevice_many net/core/dev.c:12464 [inline]
unregister_netdevice_queue net/core/dev.c:12278 [inline]
unregister_netdevice include/linux/netdevice.h:3408 [inline]
unregister_netdev+0x142/0x1b0 net/core/dev.c:12482
bnep_session+0x25d7/0x27d0 net/bluetooth/bnep/core.c:525
kthread+0x355/0x410 kernel/kthread.c:467
ret_from_fork+0x3a6/0x980 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del+0x4c/0xc0 lib/klist.c:230
Code: f5 49 89 dd 49 c1 ed 03 43 80 7c 3d 00 00 74 08 48 89 df e8 96 39 9e f5 4c 8b 33 49 83 e6 fe 49 8d 7e 58 48 89 f8 48 c1 e8 03 <42> 80 3c 38 00 74 05 e8 78 39 9e f5 4d 8b 66 58 4c 89 f7 e8 8c 16
RSP: 0018:ffffc90004d3f7e8 EFLAGS: 00010212
RAX: 000000000000000b RBX: ffff88804d043460 RCX: ffff8880243b9d00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000058
RBP: ffffc90004d3f810 R08: ffff888037d5ac33 R09: 1ffff11006fab586
R10: dffffc0000000000 R11: ffffed1006fab587 R12: ffff888050c12618
R13: 1ffff11009a0868c R14: 0000000000000000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880d9cdb000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc19c5f2160 CR3: 000000004fa9b000 CR4: 00000000000006f0
----------------
Code disassembly (best guess):
0: f5 cmc
1: 49 89 dd mov %rbx,%r13
4: 49 c1 ed 03 shr $0x3,%r13
8: 43 80 7c 3d 00 00 cmpb $0x0,0x0(%r13,%r15,1)
e: 74 08 je 0x18
10: 48 89 df mov %rbx,%rdi
13: e8 96 39 9e f5 call 0xf59e39ae
18: 4c 8b 33 mov (%rbx),%r14
1b: 49 83 e6 fe and $0xfffffffffffffffe,%r14
1f: 49 8d 7e 58 lea 0x58(%r14),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 74 05 je 0x36
31: e8 78 39 9e f5 call 0xf59e39ae
36: 4d 8b 66 58 mov 0x58(%r14),%r12
3a: 4c 89 f7 mov %r14,%rdi
3d: e8 .byte 0xe8
3e: 8c 16 mov %ss,(%rsi)
<<<<<<<<<<<<<<< tail report >>>>>>>>>>>>>>>
reply other threads:[~2026-06-26 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a3eee61.0ca26d91.74bfa.10cf@mx.google.com \
--to=sanan.hasanou@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=contact@pgazz.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.