mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "cve@kernel.org" <cve@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [External] : Re: CVE-2023-52628: netfilter: nftables: exthdr: fix 4-byte stack OOB write
Date: Tue, 9 Jul 2024 11:44:21 +0000	[thread overview]
Message-ID: <a059d0a56078b369a78cccbe60e5d538c61d76d8.camel@oracle.com> (raw)
In-Reply-To: <2024070948-helpful-departure-a468@gregkh>

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

On Tue, Jul 09 2024 at 15:39:43 +0530, gregkh@linuxfoundation.org wrote:
> Looks like Red Hat created it and then rejected it, you will have to
> talk about this with them.  But then later ZDI asked me to assign a CVE
> for it, and I did assuming that they knew what they were talking about.
> I shouldn't have assumed that :(
> 
> I don't know what to do here, sorry.  If you don't think this is an
> issue, great, I'll be glad to reject it but we should say at least why
> we don't think so here in this thread, right?

Thank you for the clarification!

I thought the "Linux kernel security team" is referring to an upstream
group, so I asked about it because it seemed off.

Anyways, best to have this up instead of not.

Thanks,
Siddh

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-07-09 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024032850-CVE-2023-52628-14fb@gregkh>
2024-07-09  3:48 ` Siddh Raman Pant
2024-07-09  5:19   ` gregkh
2024-07-09  5:27     ` [External] : " Siddh Raman Pant
2024-07-09 10:09       ` gregkh
2024-07-09 11:44         ` Siddh Raman Pant [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a059d0a56078b369a78cccbe60e5d538c61d76d8.camel@oracle.com \
    --to=siddh.raman.pant@oracle.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®