All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Qingfeng Hao <qingfeng.hao@windriver.com>
Cc: cve@kernel.org, stable@vger.kernel.org, zhe.he@windriver.com
Subject: Re: [PATCH vulns 0/1] change the sha1 for CVE-2024-26661
Date: Fri, 1 Aug 2025 09:41:19 +0200	[thread overview]
Message-ID: <2025080132-landlady-stilt-e9f2@gregkh> (raw)
In-Reply-To: <20250801040635.4190980-1-qingfeng.hao@windriver.com>

On Fri, Aug 01, 2025 at 12:06:34PM +0800, Qingfeng Hao wrote:
> There is a fix 17ba9cde11c2bfebbd70867b0a2ac4a22e573379
> introduced in v6.8 to fix the problem introduced by
> the original fix 66951d98d9bf45ba25acf37fe0747253fafdf298,
> and they together fix the CVE-2024-26661.

Those are two different things, shouldn't they get different CVE ids?

> Since this is the first time I submit the changes on vulns project,
> not sure if the changes in my patch are exact, @Greg, please point 
> out the problems if there are and I will fix them.

There's never a need to modify the .dyad or .json files (hint, you also
did not touch the .mbox file.)  they are all auto-generated from the
.sha1 file.

But again, I don't think this is correct, either this specific CVE is
not a CVE (i.e. it doesn't actually fix an issue), or we need to assign
another one, right?

thanks,

greg k-h

  parent reply	other threads:[~2025-08-01  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  4:06 [PATCH vulns 0/1] change the sha1 for CVE-2024-26661 Qingfeng Hao
2025-08-01  4:06 ` [PATCH vulns 1/1] CVE-2024-26661: change the sha1 of the cve id Qingfeng Hao
2025-08-01  7:41 ` Greg KH [this message]
2025-08-01 12:04   ` [PATCH vulns 0/1] change the sha1 for CVE-2024-26661 Hao, Qingfeng
2025-08-02  8:19     ` Greg KH
2025-08-04  7:47       ` Qingfeng Hao
2025-08-11 15:31         ` 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=2025080132-landlady-stilt-e9f2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=qingfeng.hao@windriver.com \
    --cc=stable@vger.kernel.org \
    --cc=zhe.he@windriver.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.