mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hungyu Lin <dennylin0707@gmail.com>
To: leon@kernel.org
Cc: jgg@ziepe.ca, raeds@nvidia.com, yishaih@nvidia.com,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	dennylin0707@gmail.com
Subject: [PATCH] RDMA/mlx5: Fix cntrs_max_index overflow when binding flow counters
Date: Sun, 15 Nov 2026 08:50:25 +0000	[thread overview]
Message-ID: <20261115085025.53203-1-dennylin0707@gmail.com> (raw)

counters_set_description() stores the highest counter index supplied by
the user plus one in cntrs_max_index. Both are u32, so an index of
U32_MAX wraps cntrs_max_index to zero, and the entries after it can only
raise it to their own index plus one.

mlx5_ib_read_counters() uses cntrs_max_index to check that every bound
index fits in the output buffer before it runs

	read_attr->counters_buff[desc[i].index] += ...

With the wrapped value the check passes whatever the buffer size is, and
the entry with index U32_MAX is added to memory almost 32 GiB past the
start of the buffer.

Reject an index of U32_MAX in counters_set_description(), so that
cntrs_max_index is larger than every bound index.

Fixes: 3b3233fbf02e ("IB/mlx5: Add flow counters binding support")
Cc: stable@vger.kernel.org
Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
---
 drivers/infiniband/hw/mlx5/counters.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/infiniband/hw/mlx5/counters.c b/drivers/infiniband/hw/mlx5/counters.c
index 1c25b825d0bd..742bb10adc57 100644
--- a/drivers/infiniband/hw/mlx5/counters.c
+++ b/drivers/infiniband/hw/mlx5/counters.c
@@ -1038,7 +1038,8 @@ static int counters_set_description(
 	mcounters->ncounters = ncounters;
 	/* each counter entry have both description and index pair */
 	for (i = 0; i < ncounters; i++) {
-		if (desc_data[i].description > IB_COUNTER_BYTES)
+		if (desc_data[i].description > IB_COUNTER_BYTES ||
+		    desc_data[i].index == U32_MAX)
 			return -EINVAL;

 		if (cntrs_max_index <= desc_data[i].index)
--
2.43.0

                 reply	other threads:[~2026-11-15  8:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261115085025.53203-1-dennylin0707@gmail.com \
    --to=dennylin0707@gmail.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=raeds@nvidia.com \
    --cc=yishaih@nvidia.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

all inboxes | Powered by JetHome®