From: Siddh Raman Pant <code@siddh.me>
To: "Eric Biggers" <ebiggers@kernel.org>
Cc: "David Howells" <dhowells@redhat.com>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Eric Dumazet" <edumazet@google.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
"linux-security-modules" <linux-security-module@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"linux-kernel-mentees"
<linux-kernel-mentees@lists.linuxfoundation.org>,
"syzbot+c70d87ac1d001f29a058"
<syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com>
Subject: Re: [PATCH v3] kernel/watch_queue: Make pipe NULL while clearing watch_queue
Date: Wed, 03 Aug 2022 09:26:04 +0530 [thread overview]
Message-ID: <18261d8a63a.33799d2a402802.7512018232560408914@siddh.me> (raw)
In-Reply-To: <YunKlJCDlmyn2hJ4@sol.localdomain>
On Wed, 03 Aug 2022 06:38:36 +0530 Eric Biggers <ebiggers@kernel.org> wrote:
> On Thu, Jul 28, 2022 at 09:21:21PM +0530, Siddh Raman Pant wrote:
> > If not done, a reference to a freed pipe remains in the watch_queue,
> > as this function is called before freeing a pipe in free_pipe_info()
> > (see line 834 of fs/pipe.c).
> >
> > This causes a UAF when post_one_notification() tries to access the pipe
> > on a key update, which is reported by syzbot.
> >
> > We also need to use READ_ONCE() in post_one_notification() to prevent the
> > compiler from optimising and loading a non-NULL value from wqueue->pipe.
>
> Didn't this already get fixed by the following commit?
>
> commit 353f7988dd8413c47718f7ca79c030b6fb62cfe5
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue Jul 19 11:09:01 2022 -0700
>
> watchqueue: make sure to serialize 'wqueue->defunct' properly
>
> With that, post_one_notification() only runs while the watch_queue is locked and
> not "defunct". So it's guaranteed that the pipe still exists. Any concurrent
> free_pipe_info() waits for the watch_queue to be unlocked in watch_queue_clear()
> before proceeding to free the pipe. So where is there still a bug?
It doesn't fix the dangling pointer to the freed pipe in the watch_queue, which
had caused this crash.
> >
> > Bug report: https://syzkaller.appspot.com/bug?id=1870dd7791ba05f2ea7f47f7cbdde701173973fc
> > Reported-and-tested-by: syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com
>
> If this actually does fix something, then it's mixing Fixes and Cc stable tags.
Noted.
> > diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c
> > index bb9962b33f95..617425e34252 100644
> > --- a/kernel/watch_queue.c
> > +++ b/kernel/watch_queue.c
> > @@ -99,7 +99,7 @@ static bool post_one_notification(struct watch_queue *wqueue,
> > struct watch_notification *n)
> > {
> > void *p;
> > - struct pipe_inode_info *pipe = wqueue->pipe;
> > + struct pipe_inode_info *pipe = READ_ONCE(wqueue->pipe);
> > struct pipe_buffer *buf;
> > struct page *page;
> > unsigned int head, tail, mask, note, offset, len;
> > @@ -637,6 +637,12 @@ void watch_queue_clear(struct watch_queue *wqueue)
> > spin_lock_bh(&wqueue->lock);
> > }
> >
> > + /* Clearing the watch queue, so we should clean the associated pipe. */
> > + if (wqueue->pipe) {
> > + wqueue->pipe->watch_queue = NULL;
> > + wqueue->pipe = NULL;
> > + }
> > +
> > spin_unlock_bh(&wqueue->lock);
> > rcu_read_unlock();
> > }
>
> And this is clearly the wrong fix anyway, since it makes the call to
> put_watch_queue() in free_pipe_info() never be executed. So AFAICT, this patch
> introduces a memory leak, and doesn't actually fix anything...
>
> - Eric
>
Sorry for overlooking that. wqueue->pipe->watch_queue = NULL; is unnecessary,
but wqueue->pipe = NULL; is needed.
I will send a final v4 once all issues are resolved in this thread.
Thanks,
Siddh
next prev parent reply other threads:[~2022-08-03 3:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 15:51 [PATCH v3] kernel/watch_queue: Make pipe NULL while clearing watch_queue Siddh Raman Pant
2022-08-01 9:34 ` Siddh Raman Pant
2022-08-01 10:24 ` Greg KH
2022-08-01 12:58 ` Siddh Raman Pant
2022-08-01 13:00 ` Siddh Raman Pant
2022-08-01 16:16 ` Dipanjan Das
2022-08-01 18:49 ` Siddh Raman Pant
2022-08-03 1:16 ` Eric Biggers
2022-08-03 3:58 ` Siddh Raman Pant
2022-08-03 4:10 ` Dipanjan Das
2022-08-03 1:08 ` Eric Biggers
2022-08-03 3:56 ` Siddh Raman Pant [this message]
2022-08-03 4:12 ` Eric Biggers
2022-08-03 5:13 ` Siddh Raman Pant
2022-08-03 5:41 ` Eric Biggers
2022-08-03 8:40 ` Siddh Raman Pant
2022-08-03 18:15 ` Eric Biggers
2022-08-04 8:39 ` Siddh Raman Pant
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=18261d8a63a.33799d2a402802.7512018232560408914@siddh.me \
--to=code@siddh.me \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=fmdefrancesco@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).