Blame SOURCES/CVE-2021-0920.patch

79a518
From 10bde99768d3c92f5fde1ec51f74e926fc4cf779 Mon Sep 17 00:00:00 2001
79a518
From: Artem Savkov <asavkov@redhat.com>
79a518
Date: Thu, 27 Jan 2022 11:44:06 +0100
79a518
Subject: [KPATCH CVE-2021-0920] af_unix: fix garbage collect vs MSG_PEEK
79a518
79a518
Kernels:
79a518
- 3.10.0-1160.15.2.el7
79a518
- 3.10.0-1160.21.1.el7
79a518
- 3.10.0-1160.24.1.el7
79a518
- 3.10.0-1160.25.1.el7
79a518
- 3.10.0-1160.31.1.el7
79a518
- 3.10.0-1160.36.2.el7
79a518
- 3.10.0-1160.41.1.el7
79a518
- 3.10.0-1160.42.2.el7
79a518
- 3.10.0-1160.45.1.el7
79a518
- 3.10.0-1160.49.1.el7
79a518
- 3.10.0-1160.53.1.el7
79a518
79a518
Changes since last build:
79a518
79a518
arches: x86_64 ppc64le
79a518
- af_unix.o: changed function: unix_dgram_recvmsg
79a518
- af_unix.o: changed function: unix_stream_read_generic
79a518
- garbage.o: new function: unix_peek_fds
79a518
----
79a518
79a518
Kpatch-MR: https://gitlab.com/redhat/prdsc/rhel/src/kpatch/rhel-7/-/merge_requests/18
79a518
Approved-by: Joe Lawrence (@joe.lawrence)
79a518
Approved-by: Yannick Cote (@ycote1)
79a518
Kernels:
79a518
3.10.0-1160.21.1.el7
79a518
3.10.0-1160.24.1.el7
79a518
3.10.0-1160.25.1.el7
79a518
3.10.0-1160.31.1.el7
79a518
3.10.0-1160.36.2.el7
79a518
3.10.0-1160.41.1.el7
79a518
3.10.0-1160.42.2.el7
79a518
3.10.0-1160.45.1.el7
79a518
3.10.0-1160.49.1.el7
79a518
3.10.0-1160.53.1.el7
79a518
79a518
Modifications: moved unix_peek_fds() to net/unix/garbage.c to avoid
79a518
changing unix_gc_lock scope.
79a518
79a518
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2031986
79a518
79a518
Z-MR: https://gitlab.com/redhat/rhel/src/kernel/rhel-7/-/merge_requests/379
79a518
79a518
commit ab0fd1713f1efeb2c859d32721625ea98cd9e663
79a518
Author: William Zhao <wizhao@redhat.com>
79a518
Date:   Wed Jan 19 09:29:17 2022 -0500
79a518
79a518
    af_unix: fix garbage collect vs MSG_PEEK
79a518
79a518
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2031970
79a518
    Upstream Status: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
79a518
    CVE: CVE-2021-0920
79a518
    Conflicts: The code still uses the old "sock_iocb" structure since rhel-7
79a518
    does not have the commit 7cc05662682da ("net: remove sock_iocb"). Thus
79a518
    passing the "scm_cookie" pointer to the "unix_peek_fds" was slightly
79a518
    modified to use "siocb->scm" instead of just "&scm". Additionally
79a518
    the "unix_gc_lock" is not exposed to "af_unix.c" via a header file since
79a518
    rhel-7 does not have the commit f4e65870e5ce ("net: split out functions
79a518
    related to registering inflight socket files"). Bringing in the commit
79a518
    will add a new UNIX_SCM kernel config; this can be avoided by adding
79a518
    extern-ing the "unix_gc_lock".
79a518
79a518
    commit cbcf01128d0a92e131bd09f1688fe032480b65ca
79a518
    Author: Miklos Szeredi <mszeredi@redhat.com>
79a518
    Date:   Wed Jul 28 14:47:20 2021 +0200
79a518
79a518
        af_unix: fix garbage collect vs MSG_PEEK
79a518
79a518
        unix_gc() assumes that candidate sockets can never gain an external
79a518
        reference (i.e.  be installed into an fd) while the unix_gc_lock is
79a518
        held.  Except for MSG_PEEK this is guaranteed by modifying inflight
79a518
        count under the unix_gc_lock.
79a518
79a518
        MSG_PEEK does not touch any variable protected by unix_gc_lock (file
79a518
        count is not), yet it needs to be serialized with garbage collection.
79a518
        Do this by locking/unlocking unix_gc_lock:
79a518
79a518
         1) increment file count
79a518
79a518
         2) lock/unlock barrier to make sure incremented file count is visible
79a518
            to garbage collection
79a518
79a518
         3) install file into fd
79a518
79a518
        This is a lock barrier (unlike smp_mb()) that ensures that garbage
79a518
        collection is run completely before or completely after the barrier.
79a518
79a518
        Cc: <stable@vger.kernel.org>
79a518
        Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
79a518
        Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
79a518
        Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
79a518
    Signed-off-by: William Zhao <wizhao@redhat.com>
79a518
79a518
Signed-off-by: Artem Savkov <asavkov@redhat.com>
79a518
---
79a518
 net/unix/af_unix.c |  7 +++++--
79a518
 net/unix/garbage.c | 47 ++++++++++++++++++++++++++++++++++++++++++++++
79a518
 2 files changed, 52 insertions(+), 2 deletions(-)
79a518
79a518
diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
79a518
index bcb0ad54b9b3..a264b4598872 100644
79a518
--- a/net/unix/af_unix.c
79a518
+++ b/net/unix/af_unix.c
79a518
@@ -1468,6 +1468,8 @@ out:
79a518
 	return err;
79a518
 }
79a518
 
79a518
+void unix_peek_fds(struct scm_cookie *scm, struct sk_buff *skb);
79a518
+
79a518
 static void unix_detach_fds(struct scm_cookie *scm, struct sk_buff *skb)
79a518
 {
79a518
 	int i;
79a518
@@ -2182,7 +2184,8 @@ static int unix_dgram_recvmsg(struct kiocb *iocb, struct socket *sock,
79a518
 		sk_peek_offset_fwd(sk, size);
79a518
 
79a518
 		if (UNIXCB(skb).fp)
79a518
-			siocb->scm->fp = scm_fp_dup(UNIXCB(skb).fp);
79a518
+			unix_peek_fds(siocb->scm, skb);
79a518
+
79a518
 	}
79a518
 	err = (flags & MSG_TRUNC) ? skb->len - skip : size;
79a518
 
79a518
@@ -2432,7 +2435,7 @@ unlock:
79a518
 			/* It is questionable, see note in unix_dgram_recvmsg.
79a518
 			 */
79a518
 			if (UNIXCB(skb).fp)
79a518
-				siocb->scm->fp = scm_fp_dup(UNIXCB(skb).fp);
79a518
+				unix_peek_fds(siocb->scm, skb);
79a518
 
79a518
 			sk_peek_offset_fwd(sk, chunk);
79a518
 
79a518
diff --git a/net/unix/garbage.c b/net/unix/garbage.c
79a518
index c36757e72844..f242268477ba 100644
79a518
--- a/net/unix/garbage.c
79a518
+++ b/net/unix/garbage.c
79a518
@@ -374,3 +374,50 @@ void unix_gc(void)
79a518
  out:
79a518
 	spin_unlock(&unix_gc_lock);
79a518
 }
79a518
+
79a518
+void unix_peek_fds(struct scm_cookie *scm, struct sk_buff *skb)
79a518
+{
79a518
+	scm->fp = scm_fp_dup(UNIXCB(skb).fp);
79a518
+
79a518
+	/*
79a518
+	 * Garbage collection of unix sockets starts by selecting a set of
79a518
+	 * candidate sockets which have reference only from being in flight
79a518
+	 * (total_refs == inflight_refs).  This condition is checked once during
79a518
+	 * the candidate collection phase, and candidates are marked as such, so
79a518
+	 * that non-candidates can later be ignored.  While inflight_refs is
79a518
+	 * protected by unix_gc_lock, total_refs (file count) is not, hence this
79a518
+	 * is an instantaneous decision.
79a518
+	 *
79a518
+	 * Once a candidate, however, the socket must not be reinstalled into a
79a518
+	 * file descriptor while the garbage collection is in progress.
79a518
+	 *
79a518
+	 * If the above conditions are met, then the directed graph of
79a518
+	 * candidates (*) does not change while unix_gc_lock is held.
79a518
+	 *
79a518
+	 * Any operations that changes the file count through file descriptors
79a518
+	 * (dup, close, sendmsg) does not change the graph since candidates are
79a518
+	 * not installed in fds.
79a518
+	 *
79a518
+	 * Dequeing a candidate via recvmsg would install it into an fd, but
79a518
+	 * that takes unix_gc_lock to decrement the inflight count, so it's
79a518
+	 * serialized with garbage collection.
79a518
+	 *
79a518
+	 * MSG_PEEK is special in that it does not change the inflight count,
79a518
+	 * yet does install the socket into an fd.  The following lock/unlock
79a518
+	 * pair is to ensure serialization with garbage collection.  It must be
79a518
+	 * done between incrementing the file count and installing the file into
79a518
+	 * an fd.
79a518
+	 *
79a518
+	 * If garbage collection starts after the barrier provided by the
79a518
+	 * lock/unlock, then it will see the elevated refcount and not mark this
79a518
+	 * as a candidate.  If a garbage collection is already in progress
79a518
+	 * before the file count was incremented, then the lock/unlock pair will
79a518
+	 * ensure that garbage collection is finished before progressing to
79a518
+	 * installing the fd.
79a518
+	 *
79a518
+	 * (*) A -> B where B is on the queue of A or B is on the queue of C
79a518
+	 * which is on the queue of listening socket A.
79a518
+	 */
79a518
+	spin_lock(&unix_gc_lock);
79a518
+	spin_unlock(&unix_gc_lock);
79a518
+}
79a518
-- 
79a518
2.26.3
79a518
79a518