From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: REJECTED: CVE-2022-48936: gso: do not skip outer ip header in case of ipip and net_failover
Date: Sat, 31 Aug 2024 07:38:01 +0200 [thread overview]
Message-ID: <2024083133-shale-shush-19b8@gregkh> (raw)
In-Reply-To: <ZtIritQik7Gt1t2J@eldamar.lan>
On Fri, Aug 30, 2024 at 10:28:58PM +0200, Salvatore Bonaccorso wrote:
> Hi Greg,
>
> On Fri, Aug 30, 2024 at 12:43:58PM +0200, Greg Kroah-Hartman wrote:
> >
> > CVE-2022-48936 has now been rejected and is no longer a valid CVE.
>
> While the CVE was alrady announced and the commit present in the
> vuln.s git repository for the rejection, it looks that
> https://www.cve.org/CVERecord?id=CVE-2022-48936 is still valid.
>
> Do you happen to know if this is only a temporary hickup on cve.org or
> is there still something missing for pushing it?
Odd, I don't know what went wrong. I've pushed the "reject this cve"
command to cve.org again and now it looks like it "stuck" and all should
be good.
Thanks for checking and letting me know!
greg k-h
prev parent reply other threads:[~2024-08-31 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024083059-REJECTED-7912@gregkh>
2024-08-30 20:28 ` Salvatore Bonaccorso
2024-08-31 5:38 ` Greg Kroah-Hartman [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=2024083133-shale-shush-19b8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=carnil@debian.org \
--cc=cve@kernel.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®