[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALJHwhQ8BM=WpLme2x4oKUy2+u7Q_DBeHjP2Ot6GFvvGmdr1ZQ@mail.gmail.com>
Date: Thu, 11 Jun 2020 01:14:03 +1000
From: Wade Mealing <wmealing@...hat.com>
To: oss-security@...ts.openwall.com
Subject: Re: kernel: Multiple SSBD related flaws CVE-2020-10766
, CVE-2020-10767, CVE-2020-10768
> Did you ask the authors of the patches? I think they might have already
> assigned CVEs from Google's pool, based on previous interactions with
> those developers...
I am in discussions with Anthony Steinhauser from Google, Anthony
stated there were no CVE's assigned. This message was mainly for the
other CNA's ( https://cve.mitre.org/cve/request_id.html ) who may be
able to assign CVE's.
If the kernel was a CVE Numbering Authority, they could assign their
own ( https://cve.mitre.org/cve/cna.html#become_a_cna ) and this whole
problem would not exist. I'm not on the security@...nel.org mailing
list (even after asking), so I can't really say what goes on behind
those closed doors, I would think it falls under their interests.
> thanks,
No problem.
Wade Mealing
Product Security - Kernel, RHCE
Red Hat
wmealing@...hat.com
TRIED. TESTED. TRUSTED.
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
