linux-kernel - Reminder: 2 open syzbot bugs in "security/integrity" 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: <20190709191512.GE641@sol.localdomain>
Date:   Tue, 9 Jul 2019 12:15:12 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     linux-integrity@...r.kernel.org,
        linux-security-module@...r.kernel.org,
        Mimi Zohar <zohar@...ux.ibm.com>,
        Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
        James Morris <jmorris@...ei.org>,
        "Serge E. Hallyn" <serge@...lyn.com>
Cc:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Reminder: 2 open syzbot bugs in "security/integrity" 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 2 of them as possibly being bugs in the "security/integrity" 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 "security/integrity" 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 process_measurement
Last occurred:      34 days ago
Reported:           267 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=aad04cfa9fddcc5588f8b28ddf739f9a3ebf5874
Original thread:    https://lkml.kernel.org/lkml/0000000000003302870578477029@google.com/T/#u

This bug has a C 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+5ab61747675a87ea359d@...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/0000000000003302870578477029@google.com

--------------------------------------------------------------------------------
Title:              INFO: task hung in process_measurement
Last occurred:      118 days ago
Reported:           281 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=623c2e176b9d80b1872e7559e5b823b1ec4911b6
Original thread:    https://lkml.kernel.org/lkml/00000000000033ebee0577262a98@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, 106 days ago.

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