From: "Cen Zhang (Microsoft)" <cenzhang@linux.microsoft.com>
To: David Howells <dhowells@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>, Kees Cook <kees@kernel.org>,
"Dae R . Jeong" <threeearcat@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
AutonomousCodeSecurity@microsoft.com,
tgopinath@linux.microsoft.com,
Cen Zhang <cenzhang@linux.microsoft.com>
Subject: [PATCH] watch_queue: Fix missing locking in watch_queue_set_size()
Date: Thu, 8 Oct 2026 18:42:33 -0400 [thread overview]
Message-ID: <20261008224233.9675-1-cenzhang@linux.microsoft.com> (raw)
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 does not take wqueue->lock, so the four
stores are not atomic as a group and, 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 putting the four publication stores under wqueue->lock.
post_one_notification() already runs with that lock held, so a poster now
sees either the whole pool or none of it.
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
Assisted-by: LLM
Signed-off-by: Cen Zhang (Microsoft) <cenzhang@linux.microsoft.com>
---
kernel/watch_queue.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c
index 538520861e8b..9fb3035b3ebd 100644
--- a/kernel/watch_queue.c
+++ b/kernel/watch_queue.c
@@ -294,10 +294,13 @@ long watch_queue_set_size(struct pipe_inode_info *pipe, unsigned int nr_notes)
goto error_p;
bitmap_fill(bitmap, nr_notes);
+ /* Use lock since watches may already be attached. */
+ spin_lock_bh(&wqueue->lock);
wqueue->notes = pages;
wqueue->notes_bitmap = bitmap;
wqueue->nr_pages = nr_pages;
wqueue->nr_notes = nr_notes;
+ spin_unlock_bh(&wqueue->lock);
return 0;
error_p:
--
2.55.0
next reply other threads:[~2026-10-08 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:42 Cen Zhang (Microsoft) [this message]
2026-10-09 3:59 ` Cen Zhang (Microsoft)
2026-10-09 11:05 ` Greg KH
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=20261008224233.9675-1-cenzhang@linux.microsoft.com \
--to=cenzhang@linux.microsoft.com \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=brauner@kernel.org \
--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®