linux-kernel - Re: CVE-2024-26831: net/handshake: Fix handshake_req_destroy

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] [day] [month] [year] [list]

Message-ID: <2024061357-fencing-pyromania-70a2@gregkh>
Date: Thu, 13 Jun 2024 15:59:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Vegard Nossum <vegard.nossum@...cle.com>
Cc: cve@...nel.org, linux-kernel@...r.kernel.org,
	linux-cve-announce@...r.kernel.org,
	Guenter Roeck <linux@...ck-us.net>,
	Chuck Lever <chuck.lever@...cle.com>,
	Hannes Reinecke <hare@...e.de>, Jakub Kicinski <kuba@...nel.org>,
	Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Subject: Re: CVE-2024-26831: net/handshake: Fix handshake_req_destroy_test1

On Tue, Jun 11, 2024 at 10:21:47AM +0200, Vegard Nossum wrote:
> 
> On 17/04/2024 11:44, Greg Kroah-Hartman wrote:
> > Description
> > ===========
> > 
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > net/handshake: Fix handshake_req_destroy_test1
> > 
> > Recently, handshake_req_destroy_test1 started failing:
> 
> [...]
> 
> > Affected files
> > ==============
> > 
> > The file(s) affected by this issue are:
> > 	net/handshake/handshake-test.c
> 
> Hi,
> 
> This patch
> (https://git.kernel.org/torvalds/c/4e1d71cabb19ec2586827adfc60d68689c68c194)
> fixes a kunit test; we therefore believe this is not a vulnerability.

Many systems build kunit tests into the kernels they ship to customers
(hint, a few hundred million phones have them enabled...)  So if your
system does build this one, then it is an issue for you.

If you don't build it, wonderful, not a problem!  But we can't just not
assign a CVE just because someone might not build this file, again, we
do not know use cases, which is why we have to assign CVEs for all files
that could be built as part of a kernel image (but not for the userspace
test stuff.)

thanks,

greg k-h