mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bradley Morgan <brads@mainlining.org>
To: cenzhang@linux.microsoft.com
Cc: AutonomousCodeSecurity@microsoft.com, brauner@kernel.org,
	dave@stgolabs.net, dhowells@redhat.com, kees@kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	tgopinath@linux.microsoft.com, threeearcat@gmail.com
Subject: Re: [PATCH v2] watch_queue: Fix note pool publication race in watch_queue_set_size()
Date: Sat, 10 Oct 2026 13:31:38 +0100	[thread overview]
Message-ID: <B042CCA8-1AE4-47DC-B9FB-F34B86D16461@mainlining.org> (raw)
In-Reply-To: <20261009224715.46121-1-cenzhang@linux.microsoft.com>

On 9 October 2026 23:47:15 BST, "Cen Zhang (Microsoft)"
<cenzhang@linux.microsoft.com> wrote:
>There is a race between watch_queue_set_size() and
>post_one_notification().
>watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and
>nr_notes with plain stores, and post_one_notification() reads them with
>plain loads under a different lock, so nothing orders the four stores
>against the poster's loads: depending on the build, notes can be stored
>last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch
>attach to a queue before it is sized, post_one_notification() can already
>be running on another CPU at that moment: it reads nr_notes > 0, passes
>its bounds check, and then reads notes while it is still NULL,
>dereferencing notes[0].
>
>An unprivileged user triggers this reliably by watching one of its own
>keys through a notification pipe and racing
>ioctl(IOC_WATCH_QUEUE_SET_SIZE)
>on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU,
>triggering:
>
>  BUG: kernel NULL pointer dereference, address: 0000000000000000
>  RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0
>  Call Trace:
>   __post_watch_notification+0x148/0x180
>   keyctl_setperm_key+0x119/0x130
>   do_syscall_64+0x108/0x4c0
>   entry_SYSCALL_64_after_hwframe+0x77/0x7f
>  Kernel panic - not syncing: Fatal exception in interrupt
>
>Fix this by publishing nr_notes last with smp_store_release(), and by
>reading it once with smp_load_acquire() in post_one_notification() before
>the bitmap and the page array are touched.  A poster that observes a
>non-zero nr_notes then also observes the pool behind it; one that observes
>zero drops the notification as before.

Gnarly looking bug.

>
>Fixes: c73be61cede5 ("pipe: Add general notification queue support")
>Reported-by: Dae R. Jeong <threeearcat@gmail.com>
>Closes: https://lore.kernel.org/all/ZT-S8Q7tyutcvu_q@dragonet/
>Reported-by: AutonomousCodeSecurity@microsoft.com
>Suggested-by: Dae R. Jeong <threeearcat@gmail.com>
>Assisted-by: LLM

Nit: Cc: All Applicable 
<stable@vger.kernel.org>

>Signed-off-by: Cen Zhang (Microsoft) <cenzhang@linux.microsoft.com>
>---
>v2:
> - Use smp_store_release()/smp_load_acquire() instead of lock (Dae R. Jeong).
>v1:
> - https://lore.kernel.org/all/20261008224233.9675-1-cenzhang@linux.microsoft.com/
>
> kernel/watch_queue.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
>diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c
>index 538520861e8b..932a88ac1f39 100644
>--- a/kernel/watch_queue.c
>+++ b/kernel/watch_queue.c
>@@ -101,7 +101,7 @@ static bool post_one_notification(struct watch_queue *wqueue,
> 	struct pipe_inode_info *pipe = wqueue->pipe;
> 	struct pipe_buffer *buf;
> 	struct page *page;
>-	unsigned int head, tail, note, offset, len;
>+	unsigned int head, tail, note, offset, len, nr_notes;
> 	bool done = false;
> 
> 	spin_lock_irq(&pipe->rd_wait.lock);
>@@ -111,8 +111,10 @@ static bool post_one_notification(struct watch_queue *wqueue,
> 	if (pipe_full(head, tail, pipe->ring_size))
> 		goto lost;
> 
>-	note = find_first_bit(wqueue->notes_bitmap, wqueue->nr_notes);
>-	if (note >= wqueue->nr_notes)
>+	/* Pairs with the smp_store_release() in watch_queue_set_size(). */
>+	nr_notes = smp_load_acquire(&wqueue->nr_notes);
>+	note = find_first_bit(wqueue->notes_bitmap, nr_notes);
>+	if (note >= nr_notes)
> 		goto lost;
> 
> 	page = wqueue->notes[note / WATCH_QUEUE_NOTES_PER_PAGE];
>@@ -297,7 +299,8 @@ long watch_queue_set_size(struct pipe_inode_info *pipe, unsigned int nr_notes)
> 	wqueue->notes = pages;
> 	wqueue->notes_bitmap = bitmap;
> 	wqueue->nr_pages = nr_pages;
>-	wqueue->nr_notes = nr_notes;
>+	/* Pairs with the smp_load_acquire() in post_one_notification(). */
>+	smp_store_release(&wqueue->nr_notes, nr_notes);

Looks okay to me cen, just the nit:

Reviewed-by: Bradley Morgan <brads@mainlining.org>


> 	return 0;
> 
> error_p:
>

--- Thanks!
"I'm not a very positive person" - Linus torvalds

      reply	other threads:[~2026-10-10 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 22:47 Cen Zhang (Microsoft)
2026-10-10 12:31 ` Bradley Morgan [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=B042CCA8-1AE4-47DC-B9FB-F34B86D16461@mainlining.org \
    --to=brads@mainlining.org \
    --cc=AutonomousCodeSecurity@microsoft.com \
    --cc=brauner@kernel.org \
    --cc=cenzhang@linux.microsoft.com \
    --cc=dave@stgolabs.net \
    --cc=dhowells@redhat.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tgopinath@linux.microsoft.com \
    --cc=threeearcat@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®