From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9BA25376492; Sun, 12 Apr 2026 12:50:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775998210; cv=none; b=bcRUlnhOy7JYwKiikZV1tMyUnUVUFJKpaCfMCDWUdd4hPJOAirSTRBQ269Oon1IOv0NZOcOH7+BJHAk277clrDNLUyf+z3Vd4qx3K8tMgBNODXw9RSGiwzN73sPEzdQ+eXWOjjxXo4JlD99NISwg6/Lg4Wu0CWy9GmNcme3oF3U= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775998210; c=relaxed/simple; bh=UctMIAZJjUIkI9bcFxFVqtMglx8Sn3GMHxD5PPywcD4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=n1t5y2Y2bW5LIKzoTi5CZjRLkpnKimsmW597qQu5n+9xgcJjKIGfDfYNkrhxoTeqSJfzexc1ECMTpVjGM2m/1gx+1i3RpbMO7RRqFTSzgG/jD6ROtNBeQ8P+J7q5OrNFQ0JxEe6DbZIU1P5FyNNz4fkIz2j8fsHnt3bUSp5TYT4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LVJiijhl; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="LVJiijhl" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 995D9C19424; Sun, 12 Apr 2026 12:50:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775998210; bh=UctMIAZJjUIkI9bcFxFVqtMglx8Sn3GMHxD5PPywcD4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LVJiijhlBb3b8995eHFh0+LVGq4XGVZVjQr+WlYMF2XHwIMkfeyzE1ylwx2du7s9v IVuHUNJEXwMOglYKE4m7UXDTd0cIbAlMuua0PKRlxdKNa/2Fzov2d45VdcP3Ki7M0n S318Ec8ZJFEXPRi8827HjMzU3Oc84wBf6cjbHvVasuFH1z3wizT1xmsuq9VvrBpvtQ IPjCGILrRAw6lWAcxZCcLH0QxoUyd47L8cTPXjN0VZfP8+smpznmtFaX0lAbj3+BiK 7iQM793FIGhpkTIYwn73xzpWJFRjOr/9na/QJtgUxwIbClhcbSwKPjGmzebdOhrPNW XZw+6AUJ09vGw== Date: Sun, 12 Apr 2026 15:50:05 +0300 From: Leon Romanovsky To: Junrui Luo Cc: Chengchang Tang , Junxian Huang , Jason Gunthorpe , Xi Wang , Weihang Li , Wei Xu , Shengming Shu , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, Yuhao Jiang , stable@vger.kernel.org Subject: Re: [PATCH] RDMA/hns: fix out-of-bounds write in IRQ array during configuration Message-ID: <20260412125005.GB21470@unreal> References: Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Sun, Apr 05, 2026 at 04:15:44PM +0800, Junrui Luo wrote: > hns_roce_hw_v2_get_cfg() writes IRQ vector numbers into hr_dev->irq[] > using handle->rinfo.num_vectors as the loop bound. num_vectors originates > from firmware via hclge_query_pf_resource() without validation against > the array size. > > If firmware reports more than 128 MSI-X vectors for RoCE, the loop > overflows hr_dev->irq[], corrupting adjacent struct members in the > heap-allocated hns_roce_dev structure. Is this an actual issue, or just another imagined problem? Thanks