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>,
"gregkh@kernel.org" <gregkh@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 10:42:31 +0000 [thread overview]
Message-ID: <90bbbd1083635d251b04fd03ec81a4e7e4720bc2.camel@oracle.com> (raw)
In-Reply-To: <2025072818-CVE-2025-38495-3b28@gregkh>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On Mon, 28 Jul 2025 13:22:37 +0200, Greg Kroah-Hartman wrote:
> In the Linux kernel, the following vulnerability has been resolved:
>
> HID: core: ensure the allocated report buffer can contain the reserved report ID
>
> When the report ID is not used, the low level transport drivers expect
> the first byte to be 0. However, currently the allocated buffer not
> account for that extra byte, meaning that instead of having 8 guaranteed
> bytes for implement to be working, we only have 7.
>
> The Linux kernel CVE team has assigned CVE-2025-38495 to this issue.
This commit prepares for the next commit in the patch series. See
https://lore.kernel.org/all/20250710-report-size-null-v2-0-ccf922b7c4e5@kernel.org/
The patch series has 3 commits, with the main fix being the middle
commit "HID: core: ensure __hid_request reserves the report ID as the
first byte".
Unfortunately, the 1st and 3rd commit has CVE numbers assigned to them
but not the actual fix.
Please assign CVE number to the middle commit.
Segue: Can we not have same CVE number for a patch series fixing a
vuln?
Thanks,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2025-09-30 10:42 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 [this message]
2025-09-30 10:49 ` CVE-2025-38495: HID: core: ensure the allocated report buffer can contain the reserved report ID 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
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=90bbbd1083635d251b04fd03ec81a4e7e4720bc2.camel@oracle.com \
--to=siddh.raman.pant@oracle.com \
--cc=cve@kernel.org \
--cc=gregkh@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