netdev - Reminder: 3 open syzbot reports 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]

Date:   Thu, 3 Oct 2019 21:13:45 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     linux-afs@...ts.infradead.org, David Howells <dhowells@...hat.com>
Cc:     syzkaller-bugs@...glegroups.com, netdev@...r.kernel.org
Subject: Reminder: 3 open syzbot reports 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 bug reports below.

All these bugs were seen in the last week.

Here are the bug reports:

--------------------------------------------------------------------------------
Title:              KASAN: use-after-free Read in rxrpc_send_keepalive
Last occurred:      0 days ago
Reported:           55 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=9b519f4f0bcaeb000ba93389eda00310a6020abe
Original thread:    https://lore.kernel.org/lkml/000000000000e695c1058fb26925@google.com/T/#u

This bug has a C reproducer.

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+d850c266e3df14da1d31@...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://lore.kernel.org/r/000000000000e695c1058fb26925@google.com

--------------------------------------------------------------------------------
Title:              KASAN: use-after-free Read in rxrpc_release_call
Last occurred:      6 days ago
Reported:           41 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=d53e9523b662e55aae32105864f6973e5afb6730
Original thread:    https://lore.kernel.org/lkml/000000000000727bd10590c9cf6c@google.com/T/#u

This bug has a syzkaller reproducer only.

This bug was bisected to:

		commit 2baec2c3f854d1f79c7bb28386484e144e864a14
		Author: David Howells <dhowells@...hat.com>
		Date:   Wed May 24 16:02:32 2017 +0000

		  rxrpc: Support network namespacing

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+eed305768ece6682bb7f@...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://lore.kernel.org/r/000000000000727bd10590c9cf6c@google.com

--------------------------------------------------------------------------------
Title:              KASAN: use-after-free Read in rxrpc_put_peer
Last occurred:      1 day ago
Reported:           36 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=369d7776ffde266ffe528cf8740346435362f37f
Original thread:    https://lore.kernel.org/lkml/000000000000f6a13b059132aa6c@google.com/T/#u

This bug has a C reproducer.

The original thread for this bug has received 1 reply, 35 days ago.

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+b9be979c55f2bea8ed30@...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://lore.kernel.org/r/000000000000f6a13b059132aa6c@google.com