From: Hyunwoo Kim <v4bel@theori.io>
To: "Rémi Denis-Courmont" <remi@remlab.net>
Cc: courmisch@gmail.com, imv4bel@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, v4bel@theori.io
Subject: Re: [PATCH] net: phonet: Fix Use-After-Free in pep_recvmsg
Date: Tue, 5 Dec 2023 20:25:19 -0800 [thread overview]
Message-ID: <20231206042519.GA5926@ubuntu> (raw)
In-Reply-To: <A2443BF8-D693-4182-9E07-3FFA33D97217@remlab.net>
Hi,
On Mon, Dec 04, 2023 at 09:12:11AM +0200, Rémi Denis-Courmont wrote:
> Hi,
>
> Le 4 décembre 2023 08:59:52 GMT+02:00, Hyunwoo Kim <v4bel@theori.io> a écrit :
> >Because pep_recvmsg() fetches the skb from pn->ctrlreq_queue
> >without holding the lock_sock and then frees it,
> >a race can occur with pep_ioctl().
> >A use-after-free for a skb occurs with the following flow.
>
> Isn't this the same issue that was reported by Huawei rootlab and for which I already provided a pair of patches to the security list two months ago?
Is the issue reported to the security mailing list two months ago the same as this pn->ctrlreq_queue race?
>
> TBH, I much prefer the approach in the other patch set, which takes the hit on the ioctl() side rather than the recvmsg()'s.
That's probably a patch to add sk->sk_receive_queue.lock to pep_ioctl(), is that correct?
>
> Unfortunately, I have no visibility on what happened or didn't happen after that, since the security list is private.
Perhaps this issue hasn't gotten much attention.
Regards,
Hyunwoo Kim
>
> >```
> >pep_recvmsg() -> skb_dequeue() -> skb_free_datagram()
> >pep_ioctl() -> skb_peek()
> >```
> >Fix this by adjusting the scope of lock_sock in pep_recvmsg().
> >
> >Signed-off-by: Hyunwoo Kim <v4bel@theori.io>
> >---
> > net/phonet/pep.c | 17 +++++++++++++----
> > 1 file changed, 13 insertions(+), 4 deletions(-)
> >
> >diff --git a/net/phonet/pep.c b/net/phonet/pep.c
> >index faba31f2eff2..212d8a9ddaee 100644
> >--- a/net/phonet/pep.c
> >+++ b/net/phonet/pep.c
> >@@ -1250,12 +1250,17 @@ static int pep_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
> > if (unlikely(1 << sk->sk_state & (TCPF_LISTEN | TCPF_CLOSE)))
> > return -ENOTCONN;
> >
> >+ lock_sock(sk);
> >+
> > if ((flags & MSG_OOB) || sock_flag(sk, SOCK_URGINLINE)) {
> > /* Dequeue and acknowledge control request */
> > struct pep_sock *pn = pep_sk(sk);
> >
> >- if (flags & MSG_PEEK)
> >+ if (flags & MSG_PEEK) {
> >+ release_sock(sk);
> > return -EOPNOTSUPP;
> >+ }
> >+
>
> Also this change is not really accounted for.
>
> > skb = skb_dequeue(&pn->ctrlreq_queue);
> > if (skb) {
> > pep_ctrlreq_error(sk, skb, PN_PIPE_NO_ERROR,
> >@@ -1263,12 +1268,14 @@ static int pep_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
> > msg->msg_flags |= MSG_OOB;
> > goto copy;
> > }
> >- if (flags & MSG_OOB)
> >+
> >+ if (flags & MSG_OOB) {
> >+ release_sock(sk);
> > return -EINVAL;
> >+ }
> > }
> >
> > skb = skb_recv_datagram(sk, flags, &err);
> >- lock_sock(sk);
> > if (skb == NULL) {
> > if (err == -ENOTCONN && sk->sk_state == TCP_CLOSE_WAIT)
> > err = -ECONNRESET;
> >@@ -1278,7 +1285,7 @@ static int pep_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
> >
> > if (sk->sk_state == TCP_ESTABLISHED)
> > pipe_grant_credits(sk, GFP_KERNEL);
> >- release_sock(sk);
> >+
> > copy:
> > msg->msg_flags |= MSG_EOR;
> > if (skb->len > len)
> >@@ -1291,6 +1298,8 @@ static int pep_recvmsg(struct sock *sk, struct msghdr *msg, size_t len,
> > err = (flags & MSG_TRUNC) ? skb->len : len;
> >
> > skb_free_datagram(sk, skb);
> >+
> >+ release_sock(sk);
> > return err;
> > }
> >
next prev parent reply other threads:[~2023-12-06 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 6:59 [PATCH] net: phonet: Fix Use-After-Free in pep_recvmsg Hyunwoo Kim
2023-12-04 7:12 ` Rémi Denis-Courmont
2023-12-06 4:25 ` Hyunwoo Kim [this message]
2023-12-11 16:47 ` Rémi Denis-Courmont
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=20231206042519.GA5926@ubuntu \
--to=v4bel@theori.io \
--cc=courmisch@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imv4bel@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=remi@remlab.net \
/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).