From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Chuck Lever <chuck.lever@oracle.com>,
Hannes Reinecke <hare@suse.de>, Jakub Kicinski <kuba@kernel.org>,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: CVE-2024-26831: net/handshake: Fix handshake_req_destroy_test1
Date: Thu, 13 Jun 2024 15:59:00 +0200 [thread overview]
Message-ID: <2024061357-fencing-pyromania-70a2@gregkh> (raw)
In-Reply-To: <97629d4e-1f3d-441c-b92a-2e8b74b9846a@oracle.com>
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
prev parent reply other threads:[~2024-06-13 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024041704-CVE-2024-26831-2e6e@gregkh>
2024-06-11 8:21 ` Vegard Nossum
2024-06-13 13:59 ` Greg Kroah-Hartman [this message]
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=2024061357-fencing-pyromania-70a2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chuck.lever@oracle.com \
--cc=cve@kernel.org \
--cc=hare@suse.de \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=kuba@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vegard.nossum@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 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®