From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
Ben Hutchings <ben@decadent.org.uk>,
netdev <netdev@vger.kernel.org>,
cve@kernel.org, Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: Is CVE-2024-26624 a valid issue?
Date: Wed, 27 Mar 2024 14:56:06 +0100 [thread overview]
Message-ID: <2024032743-wildfire-amusing-1875@gregkh> (raw)
In-Reply-To: <20240311140043.GR86322@google.com>
On Mon, Mar 11, 2024 at 02:00:43PM +0000, Lee Jones wrote:
> On Mon, 11 Mar 2024, Eric Dumazet wrote:
>
> > Hi Ben
> >
> > Yes, my understanding of the issue is that it is a false positive.
> >
> > Some kernels might crash whenever LOCKDEP triggers, as for any WARNing.
>
> Exactly. So is it possible to trip this, false positive or otherwise?
> Being able to crash the kernel, even under false pretences, is
> definitely something we usually provide CVE allocations for.
lockdep warnings do not trigger a reboot for panic-on-warn, so I'll go
reject this cve, thanks.
greg k-h
prev parent reply other threads:[~2024-03-27 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 0:02 Is CVE-2024-26624 a valid issue? Ben Hutchings
2024-03-11 9:47 ` Eric Dumazet
2024-03-11 14:00 ` Lee Jones
2024-03-27 13:56 ` Greg KH [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=2024032743-wildfire-amusing-1875@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=cve@kernel.org \
--cc=edumazet@google.com \
--cc=lee@kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).