mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Zhiyu Zhang <zhiyuzhang999@gmail.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	brauner@kernel.org, dhowells@redhat.com,
	keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
	security@kernel.org, edumazet@kernel.org, ncardwell@google.com,
	lyutoon@gmail.com, tpluszz77@gmail.com
Subject: Re: [BUG] watch_queue: RCU/info_id overlap leaks kernel stack
Date: Thu, 29 Oct 2026 07:43:43 +0100	[thread overview]
Message-ID: <2026102915-safeness-snazzy-a36d@gregkh> (raw)
In-Reply-To: <CALf2hKty86GatQ01C30j20oa+TeVdJRvbX=a_+0Rga33woJ6Lw@mail.gmail.com>

On Thu, Oct 29, 2026 at 01:06:28AM +0800, Zhiyu Zhang wrote:
> We will send the reproducers (including the complete exp for lpe) to you
> and the relevant maintainers privately. I understand your point that a
> similar reproducer can likely be recreated with a few LLM prompts.
> Nevertheless, Documentation/process/security-bugs.rst says not to
> publish a reproducer for an AI-assisted finding, so we are keeping it off-list.
> The same guidance says that AI-assisted findings must be treated as public,
> which is why the report was posted publicly.

The documentation also says that a patch should be sent which I can't
seem to find here, am I missing it somewhere?

thanks,

greg k-h

      reply	other threads:[~2026-10-29  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 15:41 Zhiyu Zhang
2026-10-28 15:56 ` Jarkko Sakkinen
2026-10-28 17:06   ` Zhiyu Zhang
2026-10-29  6:43     ` 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=2026102915-safeness-snazzy-a36d@gregkh \
    --to=greg@kroah.com \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=edumazet@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyutoon@gmail.com \
    --cc=ncardwell@google.com \
    --cc=security@kernel.org \
    --cc=tpluszz77@gmail.com \
    --cc=zhiyuzhang999@gmail.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®