Blame SOURCES/CVE-2021-4028.patch

cea510
From 44d6b1169915913fae640dada5ed931dffff6772 Mon Sep 17 00:00:00 2001
cea510
From: "C. Erastus Toe" <ctoe@redhat.com>
cea510
Date: Fri, 18 Feb 2022 01:09:25 -0500
cea510
Subject: [KPATCH CVE-2021-4028] kpatch fixes for CVE-2021-4028
cea510
cea510
Kernels:
cea510
3.10.0-1160.21.1.el7
cea510
3.10.0-1160.24.1.el7
cea510
3.10.0-1160.25.1.el7
cea510
3.10.0-1160.31.1.el7
cea510
3.10.0-1160.36.2.el7
cea510
3.10.0-1160.41.1.el7
cea510
3.10.0-1160.42.2.el7
cea510
3.10.0-1160.45.1.el7
cea510
3.10.0-1160.49.1.el7
cea510
3.10.0-1160.53.1.el7
cea510
cea510
Changes since last build:
cea510
arches: x86_64 ppc64le
cea510
cma.o: changed function: rdma_listen
cea510
---------------------------
cea510
cea510
Kpatch-MR: https://gitlab.com/redhat/prdsc/rhel/src/kpatch/rhel-7/-/merge_requests/25
cea510
Approved-by: Joe Lawrence (@joe.lawrence)
cea510
Modifications: none
cea510
cea510
commit 00225da7d36440d257a98004ee2e7f288486245b
cea510
Author: Kamal Heib <kheib@redhat.com>
cea510
Date:   Sun Jan 16 11:38:26 2022 +0200
cea510
cea510
    RDMA/cma: Do not change route.addr.src_addr.ss_family
cea510
cea510
    Bugzilla: http://bugzilla.redhat.com/2032075
cea510
    CVE: CVE-2021-4028
cea510
    Conflicts:
cea510
    The conditional statement to verify RDMA_CM_IDLE state is a
cea510
    little bit different from the upstream to 7.9.z source. The commit
cea510
    732d41c545bb (RDMA/cma: Make the locking for automatic state transition
cea510
    more clear) is missing from 7.9.z. So, the context has been modified.
cea510
cea510
    commit bc0bdc5afaa740d782fbf936aaeebd65e5c2921d
cea510
    Author: Jason Gunthorpe <jgg@nvidia.com>
cea510
    Date:   Wed Sep 15 17:21:43 2021 -0300
cea510
cea510
        RDMA/cma: Do not change route.addr.src_addr.ss_family
cea510
cea510
        If the state is not idle then rdma_bind_addr() will immediately fail and
cea510
        no change to global state should happen.
cea510
cea510
        For instance if the state is already RDMA_CM_LISTEN then this will corrupt
cea510
        the src_addr and would cause the test in cma_cancel_operation():
cea510
cea510
                        if (cma_any_addr(cma_src_addr(id_priv)) && !id_priv->cma_dev)
cea510
cea510
        To view a mangled src_addr, eg with a IPv6 loopback address but an IPv4
cea510
        family, failing the test.
cea510
cea510
        This would manifest as this trace from syzkaller:
cea510
cea510
          BUG: KASAN: use-after-free in __list_add_valid+0x93/0xa0 lib/list_debug.c:26
cea510
          Read of size 8 at addr ffff8881546491e0 by task syz-executor.1/32204
cea510
cea510
          CPU: 1 PID: 32204 Comm: syz-executor.1 Not tainted 5.12.0-rc8-syzkaller #0
cea510
          Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
cea510
          Call Trace:
cea510
           __dump_stack lib/dump_stack.c:79 [inline]
cea510
           dump_stack+0x141/0x1d7 lib/dump_stack.c:120
cea510
           print_address_description.constprop.0.cold+0x5b/0x2f8 mm/kasan/report.c:232
cea510
           __kasan_report mm/kasan/report.c:399 [inline]
cea510
           kasan_report.cold+0x7c/0xd8 mm/kasan/report.c:416
cea510
           __list_add_valid+0x93/0xa0 lib/list_debug.c:26
cea510
           __list_add include/linux/list.h:67 [inline]
cea510
           list_add_tail include/linux/list.h:100 [inline]
cea510
           cma_listen_on_all drivers/infiniband/core/cma.c:2557 [inline]
cea510
           rdma_listen+0x787/0xe00 drivers/infiniband/core/cma.c:3751
cea510
           ucma_listen+0x16a/0x210 drivers/infiniband/core/ucma.c:1102
cea510
           ucma_write+0x259/0x350 drivers/infiniband/core/ucma.c:1732
cea510
           vfs_write+0x28e/0xa30 fs/read_write.c:603
cea510
           ksys_write+0x1ee/0x250 fs/read_write.c:658
cea510
           do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
cea510
           entry_SYSCALL_64_after_hwframe+0x44/0xae
cea510
cea510
        Which is indicating that an rdma_id_private was destroyed without doing
cea510
        cma_cancel_listens().
cea510
cea510
        Instead of trying to re-use the src_addr memory to indirectly create an
cea510
        any address build one explicitly on the stack and bind to that as any
cea510
        other normal flow would do.
cea510
cea510
        Link: https://lore.kernel.org/r/0-v1-9fbb33f5e201+2a-cma_listen_jgg@nvidia.com
cea510
        Cc: stable@vger.kernel.org
cea510
        Fixes: 732d41c545bb ("RDMA/cma: Make the locking for automatic state transition more clear")
cea510
        Reported-by: syzbot+6bb0528b13611047209c@syzkaller.appspotmail.com
cea510
        Tested-by: Hao Sun <sunhao.th@gmail.com>
cea510
        Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
cea510
        Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
cea510
cea510
    Signed-off-by: Kamal Heib <kheib@redhat.com>
cea510
cea510
Signed-off-by: C. Erastus Toe <ctoe@redhat.com>
cea510
---
cea510
 drivers/infiniband/core/cma.c | 9 +++++++--
cea510
 1 file changed, 7 insertions(+), 2 deletions(-)
cea510
cea510
diff --git a/drivers/infiniband/core/cma.c b/drivers/infiniband/core/cma.c
cea510
index ec473099e445..935f3979c8e2 100644
cea510
--- a/drivers/infiniband/core/cma.c
cea510
+++ b/drivers/infiniband/core/cma.c
cea510
@@ -3467,8 +3467,13 @@ int rdma_listen(struct rdma_cm_id *id, int backlog)
cea510
 
cea510
 	id_priv = container_of(id, struct rdma_id_private, id);
cea510
 	if (id_priv->state == RDMA_CM_IDLE) {
cea510
-		id->route.addr.src_addr.ss_family = AF_INET;
cea510
-		ret = rdma_bind_addr(id, cma_src_addr(id_priv));
cea510
+		struct sockaddr_in any_in = {
cea510
+			.sin_family = AF_INET,
cea510
+			.sin_addr.s_addr = htonl(INADDR_ANY),
cea510
+		};
cea510
+
cea510
+		/* For a well behaved ULP state will be RDMA_CM_IDLE */
cea510
+		ret = rdma_bind_addr(id, (struct sockaddr *)&any_in);
cea510
 		if (ret)
cea510
 			return ret;
cea510
 	}
cea510
-- 
cea510
2.26.3
cea510
cea510