From: Greg KH <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: cve@kernel.org, vegard.nossum@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CVE-2024-26929: Add vulnerable commit information
Date: Fri, 3 Jan 2025 07:52:15 +0100 [thread overview]
Message-ID: <2025010329-kelp-chump-18ac@gregkh> (raw)
In-Reply-To: <20250102204826.4132786-1-harshit.m.mogalapalli@oracle.com>
On Thu, Jan 02, 2025 at 12:48:26PM -0800, Harshit Mogalapalli wrote:
> This CVE fixes: 4895009c4bb7 ("scsi: qla2xxx: Prevent command send on
> chip reset") so add that information in vulnerable commit.
>
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
> ---
> cve/published/2024/CVE-2024-26929.vulnerable | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 cve/published/2024/CVE-2024-26929.vulnerable
>
> diff --git a/cve/published/2024/CVE-2024-26929.vulnerable b/cve/published/2024/CVE-2024-26929.vulnerable
> new file mode 100644
> index 000000000000..b946d6f2786b
> --- /dev/null
> +++ b/cve/published/2024/CVE-2024-26929.vulnerable
> @@ -0,0 +1 @@
> +4895009c4bb72f71f2e682f1e7d2c2d96e482087
> --
> 2.46.0
>
>
Ok, by doing this it means this whole CVE needs to be rejected as the
vulnerable commit never shows up in a a release on its own. Are you
sure about this? If so, let's just reject the CVE.
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-03 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 20:48 [PATCH] CVE-2024-26929: Add vulnerable commit information Harshit Mogalapalli
2025-01-03 6:52 ` Greg KH [this message]
2025-01-03 8:23 ` Harshit Mogalapalli
2025-01-06 16:25 ` Greg KH
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=2025010329-kelp-chump-18ac@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@oracle.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 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.