[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8EvnDtwz6Hlq/Qs@kroah.com>
Date: Fri, 13 Jan 2023 11:17:00 +0100
From: Greg KH <greg@...ah.com>
To: oss-security@...ts.openwall.com
Subject: Re: CVE-2023-0122: Linux kernel: Pre-Auth Remote DoS
in NVMe
On Thu, Jan 12, 2023 at 01:24:38PM -0600, John Helmert III wrote:
> On Thu, Jan 12, 2023 at 06:10:23PM +0100, Greg KH wrote:
> > On Thu, Jan 12, 2023 at 04:12:30PM +0200, Tal Lossos wrote:
> > > Hi all,
> > >
> > > # Description
> > > A NULL Pointer Dereference bug in nvmet_setup_auth
> > > (drivers/nvme/target/auth.c) can be triggered remotely to cause a DoS.
> > > Since the bug occurs in the authentication feature, it can be easily
> > > triggered by an unauthorized client in the pre-auth stage.
> > > Versions affected - v6.0-rc1 to v6.0-rc3 (fixed in v6.0-rc4).
> >
> > Meta-comment, why are CVE's being assigned for issues found, and then
> > fixed, in development kernel releases? Who assigned this CVE, MITRE or
> > someone else?
>
> This information used to be available for "reserved" CVEs in the JSON
> data in [1], but now that that's retired I'm not sure this is made
> public anywhere.
>
> [1] https://github.com/CVEProject/cvelistV5
So if we don't know who allocated it, we can't know who to ask to get it
revoked?
{sigh}
Yet-another reason why I hate CVEs...
greg k-h
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.
