lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <883ad6064549f85dc56b2669bc3f395191b3da9b.camel@oracle.com>
Date: Tue, 30 Sep 2025 11:09:50 +0000
From: Siddh Raman Pant <siddh.raman.pant@...cle.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "cve@...nel.org" <cve@...nel.org>,
        "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: Re: CVE-2025-38495: HID: core: ensure the allocated report buffer can
 contain the reserved report ID

On Tue, Sep 30 2025 at 16:29:03 +0530, gregkh@...uxfoundation.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.

Thanks,
Siddh

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ