linux-kernel - Re: crypto: api - Fix use-after-free and race in crypto_spawn

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: <44b4aa3d-0d3b-c10a-7d79-5fcc4d76fe98@web.de>
Date:   Fri, 10 Apr 2020 11:18:23 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Herbert Xu <herbert@...dor.apana.org.au>,
        linux-crypto@...r.kernel.org, netdev@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        syzbot+fc0674cde00b66844470@...kaller.appspotmail.com,
        syzkaller-bugs@...glegroups.com,
        "David S. Miller" <davem@...emloft.net>
Subject: Re: crypto: api - Fix use-after-free and race in crypto_spawn_alg

> Secondly the setting of the DYING flag is racy because we hold
> the read-lock instead of the write-lock.  We should instead call

Would an imperative wording be preferred for this change description?


> This patch fixes both problems.

Will another wording alternative become relevant?

Are the provided tags sufficient for such information?

Regards,
Markus