From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 697D8ECAAA1 for ; Tue, 30 Aug 2022 06:41:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229447AbiH3GlT (ORCPT ); Tue, 30 Aug 2022 02:41:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52086 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230242AbiH3GlJ (ORCPT ); Tue, 30 Aug 2022 02:41:09 -0400 Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7E51606B3 for ; Mon, 29 Aug 2022 23:41:07 -0700 (PDT) Received: by mail-ed1-f45.google.com with SMTP id a36so9073091edf.5 for ; Mon, 29 Aug 2022 23:41:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:from:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=UxYTqdIzScSvpUI5g5mfJwDHSc/0aTW3uQz89psiUFM=; b=0UpNeOEj390aG6O6jaY+zSwJfGNbVKfkhwav3BoqktoWv4MVZ+grEEk8pjSuBigtUV NfCruObfetO/uK0wHqEuqx89U2+o4PrDjAGfXklwhgSFKp89WjiWTvdFV/sQ/IJfeV10 P9erE6/vGYOA+ZxAa9OE7+UX59rO05Gb48wsX2epIG28rBDdivyqafyn1iRt47fmP55Z 5yKu1XEWUV8wkKSB/IrDLQcjhPYOxoW2jLFcOkmbQ/dKgv+7ou1wFW+wh6gt/fnSbh6D WuptFTKMMU7/TH7M9zSgaqMjLc73EY5vZtOdpGr33uhaILk6s2yIunZ6t5vRFWeumAHL HRTg== X-Gm-Message-State: ACgBeo07YYDJPlo0RQwbD/UKwBbTDH3+m+U3TVDy5bAmWL8rTMDq1Dt0 5i5WNVV8cO60Any0xGeIlfHcd3xHgVbLwQ== X-Google-Smtp-Source: AA6agR6lOBP9afiAtD8EIPeY0NHw4fUB6Cfy3UOlsbMsTIE0EAeD+VMBDV1Y4r/jkfnA3LmfTLu2sg== X-Received: by 2002:a05:6402:2a06:b0:447:820a:1afe with SMTP id ey6-20020a0564022a0600b00447820a1afemr19353151edb.291.1661841666462; Mon, 29 Aug 2022 23:41:06 -0700 (PDT) Received: from ?IPV6:2a0b:e7c0:0:107::70f? ([2a0b:e7c0:0:107::70f]) by smtp.gmail.com with ESMTPSA id vs3-20020a170907138300b007317ad372c0sm5343815ejb.20.2022.08.29.23.41.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 29 Aug 2022 23:41:05 -0700 (PDT) Message-ID: <3b8f7b37-c69d-15ae-3f23-ce4d7cabe915@kernel.org> Date: Tue, 30 Aug 2022 08:41:04 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 From: Jiri Slaby Subject: Re: [syzbot] BUG: unable to handle kernel NULL pointer dereference in tty_ldisc_receive_buf To: syzbot , gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com References: <000000000000e51e3e05e6ff44db@google.com> Content-Language: en-US In-Reply-To: <000000000000e51e3e05e6ff44db@google.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org One more try w/o wrapping: #syz dup: BUG: unable to handle kernel NULL pointer dereference in gsmld_receive_buf On 24. 08. 22, 18:35, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 1c23f9e627a7 Linux 6.0-rc2 > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci > console output: https://syzkaller.appspot.com/x/log.txt?x=177ac367080000 > kernel config: https://syzkaller.appspot.com/x/.config?x=3045c937aad027f7 > dashboard link: https://syzkaller.appspot.com/bug?extid=be4b95faeb7a9073bb88 > compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 > userspace arch: arm64 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1701758d080000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17473aad080000 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+be4b95faeb7a9073bb88@syzkaller.appspotmail.com > > Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 > Mem abort info: > ESR = 0x0000000086000006 > EC = 0x21: IABT (current EL), IL = 32 bits > SET = 0, FnV = 0 > EA = 0, S1PTW = 0 > FSC = 0x06: level 2 translation fault > user pgtable: 4k pages, 48-bit VAs, pgdp=000000010b44f000 > [0000000000000000] pgd=080000010b5f3003, p4d=080000010b5f3003, pud=080000010b1ce003, pmd=0000000000000000 > Internal error: Oops: 86000006 [#1] PREEMPT SMP > Modules linked in: > CPU: 1 PID: 28 Comm: kworker/u4:1 Not tainted 6.0.0-rc2-syzkaller-16440-g1c23f9e627a7 #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/20/2022 > Workqueue: events_unbound flush_to_ldisc > pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) > pc : 0x0 > lr : gsmld_receive_buf+0x140/0x214 drivers/tty/n_gsm.c:2861 > sp : ffff80000f603c30 > x29: ffff80000f603c40 x28: 0000000000000000 x27: 00000000000003d9 > x26: 0000000000000000 x25: 0000000000000000 x24: ffff80000d937000 > x23: ffff80000d681e40 x22: ffff0000c929b800 x21: 0000000000000000 > x20: ffff80000c205988 x19: ffff0000c91cf446 x18: ffff80000d2dec40 > x17: 0000000000000008 x16: 0000000000000000 x15: 0000000000000000 > x14: 0000000000000000 x13: 0000000000000004 x12: ffff80000d681e78 > x11: ff808000098e7e04 x10: 0000000000000000 x9 : ffff8000098e7e04 > x8 : 0000000000000000 x7 : ffff8000098dac3c x6 : 0000000000000000 > x5 : 0000000000000000 x4 : 0000000000000001 x3 : 00000000000003da > x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c929b800 > Call trace: > 0x0 > tty_ldisc_receive_buf+0xb8/0xcc drivers/tty/tty_buffer.c:461 > tty_port_default_receive_buf+0x54/0x8c drivers/tty/tty_port.c:39 > receive_buf drivers/tty/tty_buffer.c:511 [inline] > flush_to_ldisc+0x150/0x358 drivers/tty/tty_buffer.c:561 > process_one_work+0x2d8/0x504 kernel/workqueue.c:2289 > worker_thread+0x340/0x610 kernel/workqueue.c:2436 > kthread+0x12c/0x158 kernel/kthread.c:376 > ret_from_fork+0x10/0x20 > Code: bad PC value > ---[ end trace 0000000000000000 ]--- > > > --- > 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. > syzbot can test patches for this issue, for details see: > https://goo.gl/tpsmEJ#testing-patches -- js suse labs -- js suse labs