linux-kernel - Reminder: 4 open syzbot bugs in tty 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: <20190627035555.GE721@sol.localdomain>
Date:   Wed, 26 Jun 2019 20:55:55 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.com>,
        DaeRyong Jeong <threeearcat@...il.com>
Cc:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Reminder: 4 open syzbot bugs in tty subsystem

[This email was generated by a script.  Let me know if you have any suggestions
to make it better.]

Of the currently open syzbot reports against the upstream kernel, I've manually
marked 4 of them as possibly being bugs in the tty 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 4 bugs, 2 were seen in mainline in the last week.

Of these 4 bugs, 1 was bisected to a commit from the following person:

	DaeRyong Jeong <threeearcat@...il.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 tty subsystem, please let me know,
and if possible forward the report to the correct people or mailing list.

Here are the bugs:

--------------------------------------------------------------------------------
Title:              possible deadlock in console_unlock
Last occurred:      0 days ago
Reported:           385 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=39ea6caa479af471183997376dc7e90bc7d64a6a
Original thread:    https://lkml.kernel.org/lkml/00000000000087008b056df8fbb3@google.com/T/#u

This bug has a C reproducer.

The original thread for this bug received 19 replies; the last was 126 days ago.

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+43e93968b964e369db0b@...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/00000000000087008b056df8fbb3@google.com

--------------------------------------------------------------------------------
Title:              possible deadlock in console_lock_spinning_enable
Last occurred:      0 days ago
Reported:           6 days ago
Branches:           Mainline
Dashboard link:     https://syzkaller.appspot.com/bug?id=2820deb61d92a8d7ab17a56ced58e963e65d76d0
Original thread:    https://lkml.kernel.org/lkml/0000000000006c95c1058bbf7c3d@google.com/T/#u

This bug has a C reproducer.

This bug was bisected to:

	commit b6da31b2c07c46f2dcad1d86caa835227a16d9ff
	Author: DaeRyong Jeong <threeearcat@...il.com>
	Date:   Mon Apr 30 15:27:04 2018 +0000

	  tty: Fix data race in tty_insert_flip_string_fixed_flag

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+3ed715090790806d8b18@...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/0000000000006c95c1058bbf7c3d@google.com

--------------------------------------------------------------------------------
Title:              memory leak in cfserl_create
Last occurred:      21 days ago
Reported:           21 days ago
Branches:           Mainline
Dashboard link:     https://syzkaller.appspot.com/bug?id=62bc71b5fa73349e2e6b6280eca9c9615ddeb585
Original thread:    https://lkml.kernel.org/lkml/00000000000053d7e9058a97f4ca@google.com/T/#u

This bug has a syzkaller reproducer only.

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+7ec324747ce876a29db6@...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/00000000000053d7e9058a97f4ca@google.com

--------------------------------------------------------------------------------
Title:              BUG: unable to handle kernel paging request in slhc_free
Last occurred:      62 days ago
Reported:           180 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=ca98e815aabdd1494eacb048d649ffd4fc916e2e
Original thread:    https://lkml.kernel.org/lkml/000000000000675cea057e201cbb@google.com/T/#u

This bug has a C reproducer.

syzbot has bisected this bug, but I think the bisection result is incorrect.

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

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+6c5d567447bfa30f78e2@...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/000000000000675cea057e201cbb@google.com