netdev - Reminder: 3 open syzbot bugs in "net/rxrpc" subsystem

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>] [day] [month] [year] [list]
Message-ID: <20190702062126.GA3054@sol.localdomain>
Date:   Mon, 1 Jul 2019 23:21:26 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     linux-afs@...ts.infradead.org, netdev@...r.kernel.org,
        David Howells <dhowells@...hat.com>,
        "David S. Miller" <davem@...emloft.net>
Cc:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Reminder: 3 open syzbot bugs in "net/rxrpc" subsystem

[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/rxrpc" 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.

Of these 3 bugs, 1 was seen in mainline in the last week.

Of these 3 bugs, 2 were bisected to commits from the following person:

	David Howells <dhowells@...hat.com>

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/rxrpc" 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 rxrpc_connect_call
Last occurred:      14 days ago
Reported:           159 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=41872265f1e3e0489eb0cc8762f8d48b3667afdb
Original thread:    https://lkml.kernel.org/lkml/00000000000033d5e205801b05d3@google.com/T/#u

This bug has a C reproducer.

This bug was bisected to:

	commit 46894a13599a977ac35411b536fb3e0b2feefa95
	Author: David Howells <dhowells@...hat.com>
	Date:   Thu Oct 4 08:32:28 2018 +0000

	  rxrpc: Use IPv4 addresses throught the IPv6

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+7966f2a0b2c7da8939b4@...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/00000000000033d5e205801b05d3@google.com

--------------------------------------------------------------------------------
Title:              kernel BUG at net/rxrpc/local_object.c:LINE!
Last occurred:      4 days ago
Reported:           4 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=53b6555b27af2cae74e2fbdac6cadc73f9cb18aa
Original thread:    https://lkml.kernel.org/lkml/0000000000004c2416058c594b30@google.com/T/#u

This bug has a syzkaller reproducer only.

This bug was bisected to:

	commit 46894a13599a977ac35411b536fb3e0b2feefa95
	Author: David Howells <dhowells@...hat.com>
	Date:   Thu Oct 4 08:32:28 2018 +0000

	  rxrpc: Use IPv4 addresses throught the IPv6

No one has replied to the original thread for this bug yet.

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+1e0edc4b8b7494c28450@...kaller.appspotmail.com

If you send any email or patch for this bug, please reply 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/0000000000004c2416058c594b30@google.com

--------------------------------------------------------------------------------
Title:              WARNING: locking bug in flush_workqueue_prep_pwqs
Last occurred:      9 days ago
Reported:           136 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=4ae48f9c43f87ccf9f2f270b14d5b9284dadd05c
Original thread:    https://lkml.kernel.org/lkml/0000000000005c7e6f0581f1b86a@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+0c4264acb66ea0484d11@...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/0000000000005c7e6f0581f1b86a@google.com