All of lore.kernel.org
 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 05:27:15 +0000	[thread overview]
Message-ID: <18f16d08f3946fbee0917f759a855cb070aadf44.camel@oracle.com> (raw)
In-Reply-To: <2024070926-removing-chewer-2426@gregkh>

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

On Tue, Jul 09 2024 at 10:49:59 +0530, gregkh@linuxfoundation.org
wrote:
> On Tue, Jul 09, 2024 at 03:48:29AM +0000, Siddh Raman Pant wrote:
> > Is this a duplicate of CVE-2023-4881? It was rejected with the reason:
> > 
> > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4881
> > > 
> > > ** REJECT ** CVE-2023-4881 was wrongly assigned to a bug that was
> > > deemed to be a non-security issue by the Linux kernel security team.
> 
> I don't know, where is the information about that older rejected issue?
> If this isn't an issue, we will be glad to reject it.

https://nvd.nist.gov/vuln/detail/CVE-2023-4881 (see analysis
description where it just describes the issue).

Or just https://bugzilla.redhat.com/show_bug.cgi?id=2238312

I'm unable to find a rejection reason though, maybe that's on a private
mailing list.

Thanks,
Siddh

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

  reply	other threads:[~2024-07-09  5:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  7:33 CVE-2023-52628: netfilter: nftables: exthdr: fix 4-byte stack OOB write Greg Kroah-Hartman
2024-07-09  3:48 ` Siddh Raman Pant
2024-07-09  5:19   ` gregkh
2024-07-09  5:27     ` Siddh Raman Pant [this message]
2024-07-09 10:09       ` [External] : " gregkh
2024-07-09 11:44         ` Siddh Raman Pant

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=18f16d08f3946fbee0917f759a855cb070aadf44.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.