* REJECTED: CVE-2022-48936: gso: do not skip outer ip header in case of ipip and net_failover
@ 2024-08-30 10:43 Greg Kroah-Hartman
2024-08-30 20:28 ` Salvatore Bonaccorso
0 siblings, 1 reply; 3+ messages in thread
From: Greg Kroah-Hartman @ 2024-08-30 10:43 UTC (permalink / raw)
To: linux-cve-announce; +Cc: Greg Kroah-Hartman
CVE-2022-48936 has now been rejected and is no longer a valid CVE.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: REJECTED: CVE-2022-48936: gso: do not skip outer ip header in case of ipip and net_failover
2024-08-30 10:43 REJECTED: CVE-2022-48936: gso: do not skip outer ip header in case of ipip and net_failover Greg Kroah-Hartman
@ 2024-08-30 20:28 ` Salvatore Bonaccorso
2024-08-31 5:38 ` Greg Kroah-Hartman
0 siblings, 1 reply; 3+ messages in thread
From: Salvatore Bonaccorso @ 2024-08-30 20:28 UTC (permalink / raw)
To: cve, linux-kernel; +Cc: Greg Kroah-Hartman
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?
Regards,
Salvatore
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: REJECTED: CVE-2022-48936: gso: do not skip outer ip header in case of ipip and net_failover
2024-08-30 20:28 ` Salvatore Bonaccorso
@ 2024-08-31 5:38 ` Greg Kroah-Hartman
0 siblings, 0 replies; 3+ messages in thread
From: Greg Kroah-Hartman @ 2024-08-31 5:38 UTC (permalink / raw)
To: Salvatore Bonaccorso; +Cc: cve, linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-08-31 5:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-30 10:43 REJECTED: CVE-2022-48936: gso: do not skip outer ip header in case of ipip and net_failover Greg Kroah-Hartman
2024-08-30 20:28 ` Salvatore Bonaccorso
2024-08-31 5:38 ` Greg Kroah-Hartman
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.