From: Sanan Hasanov <sanan.hasanov@Knights.ucf.edu>
To: "alex.aring@gmail.com" <alex.aring@gmail.com>,
"stefan@datenfreihafen.org" <stefan@datenfreihafen.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "syzkaller@googlegroups.com" <syzkaller@googlegroups.com>,
"contact@pgazz.com" <contact@pgazz.com>
Subject: general protection fault in nl802154_trigger_scan
Date: Mon, 27 Feb 2023 06:34:15 +0000 [thread overview]
Message-ID: <IA1PR07MB98302CDCC21F6BA664FB7298ABAF9@IA1PR07MB9830.namprd07.prod.outlook.com> (raw)
Good day, dear maintainers,
We found a bug using a modified kernel configuration file used by syzbot.
We enhanced the coverage of the configuration file using our tool, klocalizer.
Kernel Branch: 6.2.0-next-20230224
Kernel config: https://drive.google.com/file/d/1nlVJD4vp7iMOPapFzdASZQ7JSiDf6SwY/view?usp=share_link
C Reproducer: Unfortunately, there is no reproducer yet
Thank you!
Best regards,
Sanan Hasanov
general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 4 PID: 26115 Comm: syz-executor.2 Not tainted 6.2.0-next-20230224 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
RIP: 0010:nl802154_trigger_scan+0x132/0xc40
Code: 48 c1 ea 03 80 3c 02 00 0f 85 e1 09 00 00 48 8b ad f8 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7d 04 48 89 fa 48 c1 ea 03 <0f> b6 04 02 48 89 fa 83 e2 07 38 d0 7f 08 84 c0 0f 85 90 07 00 00
RSP: 0018:ffffc9000b087550 EFLAGS: 00010257
RAX: dffffc0000000000 RBX: ffffc9000b0875c0 RCX: ffffc9000df9a000
RDX: 0000000000000000 RSI: ffffffff88a65a91 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88810f098c10
R13: ffff88810f050000 R14: ffff88810f0500a0 R15: ffffc9000b0875e0
FS: 00007f7b8a7fe700(0000) GS:ffff88811a200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd3780efdc CR3: 000000004dd9e000 CR4: 0000000000350ee0
Call Trace:
<TASK>
genl_family_rcv_msg_doit.isra.0+0x1e6/0x2d0
genl_rcv_msg+0x4ff/0x7e0
netlink_rcv_skb+0x165/0x440
genl_rcv+0x28/0x40
netlink_unicast+0x547/0x7f0
netlink_sendmsg+0x92f/0xe50
sock_sendmsg+0xde/0x190
____sys_sendmsg+0x717/0x900
___sys_sendmsg+0x11d/0x1b0
__sys_sendmsg+0xfe/0x1d0
do_syscall_64+0x39/0x80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7b8b88edcd
Code: 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7b8a7fdbf8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f7b8b9bbf80 RCX: 00007f7b8b88edcd
RDX: 0000000000000000 RSI: 0000000020000380 RDI: 0000000000000004
RBP: 00007f7b8b8fc59c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd638e65bf R14: 00007ffd638e6760 R15: 00007f7b8a7fdd80
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:nl802154_trigger_scan+0x132/0xc40
Code: 48 c1 ea 03 80 3c 02 00 0f 85 e1 09 00 00 48 8b ad f8 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d 7d 04 48 89 fa 48 c1 ea 03 <0f> b6 04 02 48 89 fa 83 e2 07 38 d0 7f 08 84 c0 0f 85 90 07 00 00
RSP: 0018:ffffc9000b087550 EFLAGS: 00010257
RAX: dffffc0000000000 RBX: ffffc9000b0875c0 RCX: ffffc9000df9a000
RDX: 0000000000000000 RSI: ffffffff88a65a91 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88810f098c10
R13: ffff88810f050000 R14: ffff88810f0500a0 R15: ffffc9000b0875e0
FS: 00007f7b8a7fe700(0000) GS:ffff88811a200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd3780efdc CR3: 000000004dd9e000 CR4: 0000000000350ee0
----------------
Code disassembly (best guess):
0: 48 c1 ea 03 shr $0x3,%rdx
4: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
8: 0f 85 e1 09 00 00 jne 0x9ef
e: 48 8b ad f8 00 00 00 mov 0xf8(%rbp),%rbp
15: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1c: fc ff df
1f: 48 8d 7d 04 lea 0x4(%rbp),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 0f b6 04 02 movzbl (%rdx,%rax,1),%eax <-- trapping instruction
2e: 48 89 fa mov %rdi,%rdx
31: 83 e2 07 and $0x7,%edx
34: 38 d0 cmp %dl,%al
36: 7f 08 jg 0x40
38: 84 c0 test %al,%al
3a: 0f 85 90 07 00 00 jne 0x7d0
reply other threads:[~2023-02-27 6:34 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=IA1PR07MB98302CDCC21F6BA664FB7298ABAF9@IA1PR07MB9830.namprd07.prod.outlook.com \
--to=sanan.hasanov@knights.ucf.edu \
--cc=alex.aring@gmail.com \
--cc=contact@pgazz.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).