This is a note to let you know that I've just added the patch titled
IB/core: Avoid unsigned int overflow in sg_alloc_table
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ib-core-avoid-unsigned-int-overflow-in-sg_alloc_table.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 3c7ba5760ab8eedec01159b267bb9bfcffe522ac Mon Sep 17 00:00:00 2001
From: Mark Bloch <markb@xxxxxxxxxxxx>
Date: Thu, 27 Oct 2016 16:36:31 +0300
Subject: IB/core: Avoid unsigned int overflow in sg_alloc_table
From: Mark Bloch <markb@xxxxxxxxxxxx>
commit 3c7ba5760ab8eedec01159b267bb9bfcffe522ac upstream.
sg_alloc_table gets unsigned int as parameter while the driver
returns it as size_t. Check npages isn't greater than maximum
unsigned int.
Fixes: eeb8461e36c9 ("IB: Refactor umem to use linear SG table")
Signed-off-by: Mark Bloch <markb@xxxxxxxxxxxx>
Signed-off-by: Maor Gottlieb <maorg@xxxxxxxxxxxx>
Signed-off-by: Leon Romanovsky <leon@xxxxxxxxxx>
Signed-off-by: Doug Ledford <dledford@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/infiniband/core/umem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/infiniband/core/umem.c
+++ b/drivers/infiniband/core/umem.c
@@ -175,7 +175,7 @@ struct ib_umem *ib_umem_get(struct ib_uc
cur_base = addr & PAGE_MASK;
- if (npages == 0) {
+ if (npages == 0 || npages > UINT_MAX) {
ret = -EINVAL;
goto out;
}
Patches currently in stable-queue which might be from markb@xxxxxxxxxxxx are
queue-4.4/ib-core-avoid-unsigned-int-overflow-in-sg_alloc_table.patch
queue-4.4/ib-mlx4-check-gid_index-return-value.patch
queue-4.4/ib-cm-mark-stale-cm-id-s-whenever-the-mad-agent-was-unregistered.patch
queue-4.4/ib-mlx4-fix-create-cq-error-flow.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html