mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
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 11:32:25 +0000	[thread overview]
Message-ID: <c0d698cbcea6f46e6959ab1db07735cea76f3770.camel@oracle.com> (raw)
In-Reply-To: <2025093058-iciness-talisman-8a9f@gregkh>

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

On Tue, Sep 30 2025 at 16:52:30 +0530, gregkh@linuxfoundation.org
wrote:
> Is the CVE referenced here in the Subject line, and the git id it
> references not valid?

It is valid.

> Is there some other commit that also fixes a vulnerability
> that should also be assigned to a new CVE?

Yes: 0d0777ccaa2d46609d05b66ba0096802a2746193 which is immediately
after the commit in title, and fixes the underflow reported by
syzkaller (see [1] and the commit message for the tested-by), which is
the main bug, for which there is also a public exploit (see [2]).

[1] https://lore.kernel.org/all/686bb229.a00a0220.c7b3.0081.GAE@google.com/t/#u

[2] https://github.com/xairy/kernel-exploits/tree/master/CVE-2025-38494

Thanks,
Siddh

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-09-30 11:32 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 ` 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
2025-09-30 11:32             ` Siddh Raman Pant [this message]
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=c0d698cbcea6f46e6959ab1db07735cea76f3770.camel@oracle.com \
    --to=siddh.raman.pant@oracle.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®