lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 24 Jul 2019 10:01:51 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Joe <joego@....org>
Cc:     linux-hams <linux-hams@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>,
        Ralf Baechle <ralf@...ux-mips.org>,
        "David S. Miller" <davem@...emloft.net>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: Reminder: 3 open syzbot bugs in "net/ax25" subsystem

On Wed, Jul 24, 2019 at 5:42 AM Joe <joego@....org> wrote:
>
> Hi Eric, How do I get off of this thread? When I try to unsubscribe it
> tells me I'm not a member of the group.

Hi Joe,

If you received it via netdev or linux-hams mailing lists, here are
instructions on how to unsubscribe:
http://vger.kernel.org/vger-lists.html#netdev
http://vger.kernel.org/vger-lists.html#linux-hams



> On 7/23/19 7:40 PM, Eric Biggers wrote:
> > [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@...kaller.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@...kaller.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@...kaller.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
> >
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@...glegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/623ff230-5883-560c-22d0-3e6b0eeaba39%40mcn.org.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ