mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Zhiyu Zhang <zhiyuzhang999@gmail.com>
Cc: 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: Wed, 28 Oct 2026 17:56:01 +0200	[thread overview]
Message-ID: <auIbEZv5macfZ4aq@kernel.org> (raw)
In-Reply-To: <CALf2hKveij_sHgANY9Aktm1dPa4wfKjKNkHyp9yPbjORWFXagA@mail.gmail.com>

On Wed, Oct 28, 2026 at 11:41:35PM +0800, Zhiyu Zhang wrote:
> We have a short source reproducer, exact config and QEMU results. In
> accordance with the kernel policy, we are not posting the reproducer publicly.
> We can provide it privately if a maintainer requests it. On the vulnerable
> baseline it normally reports the canary, stack/task pointers and two agreeing
> KASLR anchors within a few seconds.

This is public nobody cares. Likely I could make the reproducec with a
couple of prompts. 

What if you instead spent some time with your "short reproducer" and figure
out how to make equal reproducer with bash and keyctl? It's a good
habbit and helps to check the relevance because you have to think things
through.

This announcement is just total waste of time and energy anyhow.

Br, Jarkko



  reply	other threads:[~2026-10-28 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 15:41 Zhiyu Zhang
2026-10-28 15:56 ` Jarkko Sakkinen [this message]
2026-10-28 17:06   ` Zhiyu Zhang
2026-10-29  6:43     ` Greg KH
2026-10-29 12:05       ` Zhiyu Zhang
2026-10-29 12:31         ` Bradley Morgan

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=auIbEZv5macfZ4aq@kernel.org \
    --to=jarkko@kernel.org \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=edumazet@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®