Thread (6 messages) 6 messages, 5 authors, 2026-06-17

RE: [Intel-wired-lan] [PATCH net v2] iavf: validate num_vsis in VIRTCHNL_OP_GET_VF_RESOURCES response

From: Romanowski, Rafal <hidden>
Date: 2026-06-17 07:49:54
Also in: intel-wired-lan, lkml, stable

-----Original Message-----
From: Intel-wired-lan <redacted> On Behalf Of Simon
Horman
Sent: Monday, May 18, 2026 8:56 PM
To: Junrui Luo <redacted>
Cc: Nguyen, Anthony L <anthony.l.nguyen@intel.com>; Kitszel, Przemyslaw
[off-list ref]; Andrew Lunn [off-list ref];
David S. Miller [off-list ref]; Eric Dumazet
[off-list ref]; Jakub Kicinski [off-list ref]; Paolo Abeni
[off-list ref]; Mitch Williams [off-list ref]; Greg Rose
[off-list ref]; intel-wired-lan@lists.osuosl.org;
netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Yuhao Jiang
[off-list ref]; stable@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net v2] iavf: validate num_vsis in
VIRTCHNL_OP_GET_VF_RESOURCES response

On Thu, May 14, 2026 at 02:55:04PM +0800, Junrui Luo wrote:
quoted
The VF allocates a fixed-size buffer for IAVF_MAX_VF_VSI (3) VSI
entries when processing a VIRTCHNL_OP_GET_VF_RESOURCES response from
the PF. However, num_vsis from the PF response is used unchecked as
the loop bound when iterating over vsi_res[] in multiple functions.

A PF sending num_vsis greater than IAVF_MAX_VF_VSI, or the received
message is shorter than num_vsis claims leads to out-of-bounds
accesses on the vsi_res[] array.

Clamp num_vsis based on the actual bytes copied from the PF response.

Fixes: 5eae00c57f5e ("i40evf: main driver core")
Reported-by: Yuhao Jiang <redacted>
Cc: stable@vger.kernel.org
Signed-off-by: Junrui Luo <redacted>
---
Changes in v2:
- Clamp num_vsis based on actual received message length instead of
IAVF_MAX_VF_VSI suggested by Przemek
- Link to v1:
https://lore.kernel.org/r/SYBPR01MB7881AF11C45AEDC0D4CA89C1AF062@SYB
PR
quoted
01MB7881.ausprd01.prod.outlook.com
Reviewed-by: Simon Horman <horms@kernel.org>

There is an AI-generated review of this patchset available on sashiko.dev.
However, I believe that the issues raised there can be considered in the context of
possible follow-up. I do not believe they should block progress of this patch.

Tested-by: Rafal Romanowski <redacted>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help