public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+895d65bfe6336a274498@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
	 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 lec_atm_close
Date: Wed, 25 Mar 2026 03:43:25 -0700	[thread overview]
Message-ID: <69c3bc4d.a70a0220.234938.004d.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    b1c803d5c816 net: airoha: Rework the code flow in airoha_r..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=135ad6da580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=71d49d824b43a0d9
dashboard link: https://syzkaller.appspot.com/bug?extid=895d65bfe6336a274498
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/09cf620a7914/disk-b1c803d5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/72906e01e665/vmlinux-b1c803d5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e1bab2219b98/bzImage-b1c803d5.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc00000001d5: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000ea8-0x0000000000000eaf]
CPU: 1 UID: 0 PID: 6673 Comm: syz.0.204 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:lec_atm_close+0x60/0x9e0 net/atm/lec.c:492
Code: 74 08 4c 89 f7 e8 30 32 56 f7 49 8b 06 48 89 44 24 10 48 8d b8 a8 0e 00 00 48 89 f8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 05 e8 f5 32 56 f7 48 8b 5c 24 10 48 c7 83 a8 0e 00
RSP: 0018:ffffc90010117c28 EFLAGS: 00010202
RAX: 00000000000001d5 RBX: dffffc0000000000 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000ea8
RBP: ffff8880573c4698 R08: ffff888055d9157f R09: 1ffff1100abb22af
R10: dffffc0000000000 R11: ffffffff8ad9b0c0 R12: ffffffff8ad9b0c0
R13: 1ffff1100abb22b3 R14: ffff888055d91650 R15: ffff888055d91598
FS:  00005555597c6500(0000) GS:ffff888125561000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30b22ff8 CR3: 0000000076908000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 vcc_destroy_socket net/atm/common.c:181 [inline]
 vcc_release+0x10f/0x580 net/atm/common.c:205
 svc_release+0x6c/0xd0 net/atm/svc.c:95
 __sock_release net/socket.c:656 [inline]
 sock_close+0xc3/0x240 net/socket.c:1448
 __fput+0x44f/0xa70 fs/file_table.c:469
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 __exit_to_user_mode_loop kernel/entry/common.c:67 [inline]
 exit_to_user_mode_loop+0xed/0x480 kernel/entry/common.c:98
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:325 [inline]
 do_syscall_64+0x32d/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe00099c799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdf9827468 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fe000c17da0 RCX: 00007fe00099c799
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fe000c17da0 R08: 00007fe000c16218 R09: 0000000000000000
R10: 00000000003fe888 R11: 0000000000000246 R12: 000000000001d068
R13: 00007fe000c1618c R14: 000000000001cfe6 R15: 00007ffdf9827570
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:lec_atm_close+0x60/0x9e0 net/atm/lec.c:492
Code: 74 08 4c 89 f7 e8 30 32 56 f7 49 8b 06 48 89 44 24 10 48 8d b8 a8 0e 00 00 48 89 f8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 05 e8 f5 32 56 f7 48 8b 5c 24 10 48 c7 83 a8 0e 00
RSP: 0018:ffffc90010117c28 EFLAGS: 00010202
RAX: 00000000000001d5 RBX: dffffc0000000000 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000ea8
RBP: ffff8880573c4698 R08: ffff888055d9157f R09: 1ffff1100abb22af
R10: dffffc0000000000 R11: ffffffff8ad9b0c0 R12: ffffffff8ad9b0c0
R13: 1ffff1100abb22b3 R14: ffff888055d91650 R15: ffff888055d91598
FS:  00005555597c6500(0000) GS:ffff888125461000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcdbc1e92f8 CR3: 0000000076908000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
   0:	74 08                	je     0xa
   2:	4c 89 f7             	mov    %r14,%rdi
   5:	e8 30 32 56 f7       	call   0xf756323a
   a:	49 8b 06             	mov    (%r14),%rax
   d:	48 89 44 24 10       	mov    %rax,0x10(%rsp)
  12:	48 8d b8 a8 0e 00 00 	lea    0xea8(%rax),%rdi
  19:	48 89 f8             	mov    %rdi,%rax
  1c:	48 c1 e8 03          	shr    $0x3,%rax
  20:	48 b9 00 00 00 00 00 	movabs $0xdffffc0000000000,%rcx
  27:	fc ff df
* 2a:	80 3c 08 00          	cmpb   $0x0,(%rax,%rcx,1) <-- trapping instruction
  2e:	74 05                	je     0x35
  30:	e8 f5 32 56 f7       	call   0xf756332a
  35:	48 8b 5c 24 10       	mov    0x10(%rsp),%rbx
  3a:	48                   	rex.W
  3b:	c7                   	.byte 0xc7
  3c:	83                   	.byte 0x83
  3d:	a8 0e                	test   $0xe,%al


---
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-03-25 10:43 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=69c3bc4d.a70a0220.234938.004d.GAE@google.com \
    --to=syzbot+895d65bfe6336a274498@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --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