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 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5EFCEC76186 for ; Wed, 24 Jul 2019 02:40:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 32CC8229ED for ; Wed, 24 Jul 2019 02:40:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563936055; bh=u7Cvk6jVXMSAqvcWR0hk7Zxrt4Xl1PZUl8KaPJQEA/I=; h=Date:From:To:Cc:Subject:List-ID:From; b=Oc4/rK5xDdvY/AdyztsZUXdfvJaiwDPcWrdVbuZCapNBXv8mjgZDZ/+WL3Q3yiUpb 49DxAfUX1itwy+bLLHeXZXFlVlsn9LO6EQSR/U5JUFvpcD1qHqfMTPzWt3KWUopdvk EiKij1RHsUdscbo1ebOgaPqUHTOqMMnLgVWI31cA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726062AbfGXCkv (ORCPT ); Tue, 23 Jul 2019 22:40:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:45982 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725372AbfGXCkv (ORCPT ); Tue, 23 Jul 2019 22:40:51 -0400 Received: from sol.localdomain (c-24-5-143-220.hsd1.ca.comcast.net [24.5.143.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7CC8221670; Wed, 24 Jul 2019 02:40:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563936050; bh=u7Cvk6jVXMSAqvcWR0hk7Zxrt4Xl1PZUl8KaPJQEA/I=; h=Date:From:To:Cc:Subject:From; b=iNRFe2zorSoa4JIguI6SlZX6QIJDREtPLTeE1n0RC/F7OF+tWdB81694/f5nmMLr9 5/J+a4klB+6SrQs7VJJim9wwMTTLBWYSlKHFhXwWs3ACF7b+JiW6buw3L6My8f9hjw TUOTOahx8rx/8w1kTRoSnVFFaLNq4EVLLnSiYG48= Date: Tue, 23 Jul 2019 19:40:49 -0700 From: Eric Biggers To: linux-hams@vger.kernel.org, netdev@vger.kernel.org, Ralf Baechle , "David S. Miller" Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Reminder: 3 open syzbot bugs in "net/ax25" subsystem Message-ID: <20190724024049.GC643@sol.localdomain> Mail-Followup-To: linux-hams@vger.kernel.org, netdev@vger.kernel.org, Ralf Baechle , "David S. Miller" , linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.12.1 (2019-06-15) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org [This email was generated by a script. Let me know if you have any suggestions to make it better, or if you want it re-generated with the latest status.] Of the currently open syzbot reports against the upstream kernel, I've manually marked 3 of them as possibly being bugs in the "net/ax25" subsystem. I've listed these reports below, sorted by an algorithm that tries to list first the reports most likely to be still valid, important, and actionable. If you believe a bug is no longer valid, please close the syzbot report by sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the original thread, as explained at https://goo.gl/tpsmEJ#status If you believe I misattributed a bug to the "net/ax25" subsystem, please let me know, and if possible forward the report to the correct people or mailing list. Here are the bugs: -------------------------------------------------------------------------------- Title: general protection fault in ax25_send_frame Last occurred: 0 days ago Reported: 204 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=1cdd5b120f129364fc8e9b2b027826cf99fa696e Original thread: https://lkml.kernel.org/lkml/0000000000009ea37c057e58d787@google.com/T/#u Unfortunately, this bug does not have a reproducer. No one replied to the original thread for this bug. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+e0b81535a27b8be39502@syzkaller.appspotmail.com If you send any email or patch for this bug, please consider replying to the original thread. For the git send-email command to use, or tips on how to reply if the thread isn't in your mailbox, see the "Reply instructions" at https://lkml.kernel.org/r/0000000000009ea37c057e58d787@google.com -------------------------------------------------------------------------------- Title: KASAN: stack-out-of-bounds Write in ax25_getname Last occurred: 90 days ago Reported: 206 days ago Branches: Mainline and others Dashboard link: https://syzkaller.appspot.com/bug?id=fb195f91dc044978c1b186f1288b1eff61edcc20 Original thread: https://lkml.kernel.org/lkml/000000000000ed4120057e2df0c6@google.com/T/#u This bug has a syzkaller reproducer only. No one replied to the original thread for this bug. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+6a29097222b4d3b8617c@syzkaller.appspotmail.com If you send any email or patch for this bug, please consider replying to the original thread. For the git send-email command to use, or tips on how to reply if the thread isn't in your mailbox, see the "Reply instructions" at https://lkml.kernel.org/r/000000000000ed4120057e2df0c6@google.com -------------------------------------------------------------------------------- Title: inconsistent lock state in ax25_std_heartbeat_expiry Last occurred: 122 days ago Reported: 120 days ago Branches: net Dashboard link: https://syzkaller.appspot.com/bug?id=9086a8eac930890b2730d6441093bd478e32913f Original thread: https://lkml.kernel.org/lkml/0000000000001b07250584efbee3@google.com/T/#u Unfortunately, this bug does not have a reproducer. The original thread for this bug received 2 replies; the last was 119 days ago. If you fix this bug, please add the following tag to the commit: Reported-by: syzbot+e350b81e95a6a214da8a@syzkaller.appspotmail.com If you send any email or patch for this bug, please consider replying to the original thread. For the git send-email command to use, or tips on how to reply if the thread isn't in your mailbox, see the "Reply instructions" at https://lkml.kernel.org/r/0000000000001b07250584efbee3@google.com