From: Greg KH <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] CVE-2024-56642: Fix wrong fixes tag.
Date: Tue, 18 Feb 2025 16:26:51 +0100 [thread overview]
Message-ID: <2025021836-sprinkler-unsocial-5697@gregkh> (raw)
In-Reply-To: <20250218143732.11095-1-siddh.raman.pant@oracle.com>
On Tue, Feb 18, 2025 at 08:07:31PM +0530, Siddh Raman Pant wrote:
> The fixes tag in the commit message is incorrect. It should be the
> commit which adds the counter, which is:
>
> 04c26faa51d1 ("tipc: wait and exit until all work queues are done")
>
> Signed-off-by: Siddh Raman Pant <siddh.raman.pant@oracle.com>
> ---
> cve/published/2024/CVE-2024-56642.vulnerable | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 cve/published/2024/CVE-2024-56642.vulnerable
>
> diff --git a/cve/published/2024/CVE-2024-56642.vulnerable b/cve/published/2024/CVE-2024-56642.vulnerable
> new file mode 100644
> index 000000000000..75eac70bd13b
> --- /dev/null
> +++ b/cve/published/2024/CVE-2024-56642.vulnerable
> @@ -0,0 +1 @@
> +04c26faa51d1e2fe71cf13c45791f5174c37f986
> --
> 2.47.2
>
Many thanks, both now applied and the cve record has been regenerated.
greg k-h
next prev parent reply other threads:[~2025-02-18 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024122737-CVE-2024-56642-71ee@gregkh>
2025-02-18 13:04 ` CVE-2024-56642: tipc: Fix use-after-free of kernel socket in cleanup_bearer() Siddh Raman Pant
2025-02-18 13:10 ` Greg KH
2025-02-18 13:53 ` [PATCH] CVE-2024-56642: Fix wrong fixes tag and function name in commit message Siddh Raman Pant
2025-02-18 14:06 ` Greg KH
2025-02-18 14:37 ` [PATCH 1/2] CVE-2024-56642: Fix wrong fixes tag Siddh Raman Pant
2025-02-18 15:26 ` Greg KH [this message]
2025-02-18 14:37 ` [PATCH 2/2] CVE-2024-56642: Fix mention of wrong function 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=2025021836-sprinkler-unsocial-5697@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siddh.raman.pant@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox