The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: "cve@kernel.org" <cve@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2025-38495: HID: core: ensure the allocated report buffer can contain the reserved report ID
Date: Tue, 30 Sep 2025 13:22:30 +0200	[thread overview]
Message-ID: <2025093058-iciness-talisman-8a9f@gregkh> (raw)
In-Reply-To: <883ad6064549f85dc56b2669bc3f395191b3da9b.camel@oracle.com>

On Tue, Sep 30, 2025 at 11:09:50AM +0000, Siddh Raman Pant wrote:
> On Tue, Sep 30 2025 at 16:29:03 +0530, gregkh@linuxfoundation.org
> wrote:
> > Then the second change is the one that gets the CVE.  Any "previous"
> > commits in a series that were preparing for the real fix are not called
> > out.  As each CVE entry says, do NOT cherry-pick, but rather always take
> > all of the commits in the stable release.
> 
> IMO it won't be nice to change an identifier now and a new ID should be
> assigned instead.

I do not understand.  We are not going to change anything here...

Let's start over.  Is the CVE referenced here in the Subject line, and
the git id it references not valid?  Does it not fix a vulnerability as
described?  Is there some other commit that also fixes a vulnerability
that should also be assigned to a new CVE?  Or is something else wrong
here?

thanks,

greg k-h

  reply	other threads:[~2025-09-30 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025072818-CVE-2025-38495-3b28@gregkh>
2025-09-30 10:42 ` CVE-2025-38495: HID: core: ensure the allocated report buffer can contain the reserved report ID Siddh Raman Pant
2025-09-30 10:49   ` gregkh
2025-09-30 10:54     ` Siddh Raman Pant
2025-09-30 10:59       ` gregkh
2025-09-30 11:09         ` Siddh Raman Pant
2025-09-30 11:22           ` gregkh [this message]
2025-09-30 11:32             ` Siddh Raman Pant
2025-09-30 11:41               ` gregkh

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=2025093058-iciness-talisman-8a9f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.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