All of lore.kernel.org
 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 12:59:03 +0200	[thread overview]
Message-ID: <2025093001-petted-boney-29c2@gregkh> (raw)
In-Reply-To: <552d5ba4368ce43b12b4aa8b01852a4d8af1bdbc.camel@oracle.com>

On Tue, Sep 30, 2025 at 10:54:06AM +0000, Siddh Raman Pant wrote:
> On Tue, Sep 30 2025 at 16:19:44 +0530, gregkh@linuxfoundation.org
> wrote:
> > What git id is that?
> 
> 0d0777ccaa2d46609d05b66ba0096802a2746193

That commit id on its own does not "fix" anything that we can see, which
is why it was not given a CVE.

> > And this commit on its own fixes a problem, so it should be a separate
> > CVE, right?
> 
> The reservation of 1st byte happens in the next commit.
> 
> Not sure why the change was broken up into two.

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.

thanks,

greg k-h

  reply	other threads:[~2025-09-30 10:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 11:22 CVE-2025-38495: HID: core: ensure the allocated report buffer can contain the reserved report ID Greg Kroah-Hartman
2025-09-30 10:42 ` Siddh Raman Pant
2025-09-30 10:49   ` gregkh
2025-09-30 10:54     ` Siddh Raman Pant
2025-09-30 10:59       ` gregkh [this message]
2025-09-30 11:09         ` Siddh Raman Pant
2025-09-30 11:22           ` gregkh
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=2025093001-petted-boney-29c2@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 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.