From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH vulns 1/2] add a .vulnerable id for CVE-2024-49888
Date: Fri, 8 Nov 2024 07:49:05 +0100 [thread overview]
Message-ID: <2024110843-french-lingo-b055@gregkh> (raw)
In-Reply-To: <20241108055118.28631-1-shung-hsi.yu@suse.com>
On Fri, Nov 08, 2024 at 01:51:13PM +0800, Shung-Hsi Yu wrote:
> Link: https://lore.kernel.org/all/klr4llu43s4osw4o7234no33k6eujo2wvpeyhft2z5zgib6zac@hvg72k5q7w3f/
> Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
> ---
> Add vulnerable commit IDs as Greg previously suggested[1].
>
> I posted analysis separately and referenced them with the Link tag
> instead of including the whole analysis in the commit message. Let me
> know if an alternative approach is preferred.
>
> 1: https://lore.kernel.org/all/2024102419-deserving-veneering-6641@gregkh/
> ---
> cve/published/2024/CVE-2024-49888.vulnerable | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 cve/published/2024/CVE-2024-49888.vulnerable
>
> diff --git a/cve/published/2024/CVE-2024-49888.vulnerable b/cve/published/2024/CVE-2024-49888.vulnerable
> new file mode 100644
> index 00000000..b7b1891d
> --- /dev/null
> +++ b/cve/published/2024/CVE-2024-49888.vulnerable
> @@ -0,0 +1 @@
> +ec0e2da95f72
> --
> 2.47.0
>
>
Thanks for both of these patches. I've now applied them and pushed out
the update .json files to cve.org for these entries.
greg k-h
prev parent reply other threads:[~2024-11-08 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 5:51 Shung-Hsi Yu
2024-11-08 5:51 ` [PATCH vulns 2/2] add a .vulnerable id for CVE-2024-50063 Shung-Hsi Yu
2024-11-08 6:49 ` 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=2024110843-french-lingo-b055@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shung-hsi.yu@suse.com \
/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®