Netdev List
 help / color / mirror / Atom feed
From: syzbot <syzbot+9fdcc9f05a98a540b816@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	 horms@kernel.org, idosch@nvidia.com, kuba@kernel.org,
	 linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com,  syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] general protection fault in arp_create (4)
Date: Sun, 17 May 2026 09:54:28 -0700	[thread overview]
Message-ID: <6a09f2c4.a00a0220.300e5b.000a.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    70eda68668d1 Merge tag 'hid-for-linus-2026051401' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f56e36580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4caf64b1ee83dac0
dashboard link: https://syzkaller.appspot.com/bug?extid=9fdcc9f05a98a540b816
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6f3c10169d74/disk-70eda686.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/67977be60189/vmlinux-70eda686.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cf642084f321/bzImage-70eda686.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000016: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7]
CPU: 1 UID: 0 PID: 37 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: bat_events batadv_bla_periodic_work
RIP: 0010:arp_create+0xb1/0x980 net/ipv4/arp.c:554
Code: 89 4c 24 78 4a 89 04 21 e8 8c f7 a0 f7 44 89 b4 24 a0 00 00 00 89 9c 24 b0 00 00 00 49 8d bf b4 00 00 00 48 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 9f b4 00 00 00 49
RSP: 0018:ffffc90000ad7720 EFLAGS: 00010213
RAX: 0000000000000016 RBX: 0000000000000000 RCX: ffff8880202edc40
RDX: 0000000000000000 RSI: 0000000000000806 RDI: 00000000000000b4
RBP: ffffc90000ad7840 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff5200015af20 R12: dffffc0000000000
R13: ffff88806501d0a0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88812538a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000032000 CR3: 0000000022ee7000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 batadv_bla_send_claim+0x183/0xeb0 net/batman-adv/bridge_loop_avoidance.c:361
 batadv_bla_send_loopdetect net/batman-adv/bridge_loop_avoidance.c:1402 [inline]
 batadv_bla_periodic_work+0x654/0xae0 net/batman-adv/bridge_loop_avoidance.c:1492
 process_one_work kernel/workqueue.c:3314 [inline]
 process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397
 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478
 kthread+0x389/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:arp_create+0xb1/0x980 net/ipv4/arp.c:554
Code: 89 4c 24 78 4a 89 04 21 e8 8c f7 a0 f7 44 89 b4 24 a0 00 00 00 89 9c 24 b0 00 00 00 49 8d bf b4 00 00 00 48 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 9f b4 00 00 00 49
RSP: 0018:ffffc90000ad7720 EFLAGS: 00010213
RAX: 0000000000000016 RBX: 0000000000000000 RCX: ffff8880202edc40
RDX: 0000000000000000 RSI: 0000000000000806 RDI: 00000000000000b4
RBP: ffffc90000ad7840 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff5200015af20 R12: dffffc0000000000
R13: ffff88806501d0a0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88812538a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000032000 CR3: 0000000022ee7000 CR4: 0000000000350ef0
----------------
Code disassembly (best guess):
   0:	89 4c 24 78          	mov    %ecx,0x78(%rsp)
   4:	4a 89 04 21          	mov    %rax,(%rcx,%r12,1)
   8:	e8 8c f7 a0 f7       	call   0xf7a0f799
   d:	44 89 b4 24 a0 00 00 	mov    %r14d,0xa0(%rsp)
  14:	00
  15:	89 9c 24 b0 00 00 00 	mov    %ebx,0xb0(%rsp)
  1c:	49 8d bf b4 00 00 00 	lea    0xb4(%r15),%rdi
  23:	48 89 f8             	mov    %rdi,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	42 0f b6 04 20       	movzbl (%rax,%r12,1),%eax <-- trapping instruction
  2f:	84 c0                	test   %al,%al
  31:	0f 85 15 06 00 00    	jne    0x64c
  37:	41 0f b7 9f b4 00 00 	movzwl 0xb4(%r15),%ebx
  3e:	00
  3f:	49                   	rex.WB


---
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 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

             reply	other threads:[~2026-05-17 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 16:54 syzbot [this message]
2026-05-19  6:40 ` [syzbot] [net?] general protection fault in arp_create (4) Ido Schimmel

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=6a09f2c4.a00a0220.300e5b.000a.GAE@google.com \
    --to=syzbot+9fdcc9f05a98a540b816@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller-bugs@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