From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 929AFC5AD49 for ; Wed, 4 Jun 2025 01:03:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 4F7FD419AB; Wed, 4 Jun 2025 01:03:49 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id MyoBRhyZz6b9; Wed, 4 Jun 2025 01:03:48 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=140.211.166.142; helo=lists1.osuosl.org; envelope-from=intel-wired-lan-bounces@osuosl.org; receiver= DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 89D7741A0A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1748999028; bh=e7cwIelMI1kMqI+YiIX14tzPbkfj5YVwSEM8f2cbbyg=; h=From:To:Cc:Date:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=TqJVxaMhJfSWg/YGgA1R+pZiSZPLQRO3RzyvpeECVyFF4PCIjtYw/uHziy5R/UD4X 0VJ8PtrdpuLb5Z9UZSJxpi/2wFPE2Vr84VdkxRD7fjd4tdUUPx1JQla57s805m3xd0 BPPUQklgSPaauLvf/PZ6Ut0wlUE53/wWq+BbB6yUpjVRGActbuXGAcPztxPcnh1TQE zBZLZVh6r40lH1EtVjDenuvaGvhX9/GF55F0Q+ljF4LjdW7iWXHdQsUgMRV4drzB6z 99HS/XONJIEoqWYqQQYhxb3+7J81jg8c1cIyE3yFyVe0eJA7ejOPD+sW9WdxyTqjx5 6wzPzO/8rKqCw== Received: from lists1.osuosl.org (lists1.osuosl.org [140.211.166.142]) by smtp4.osuosl.org (Postfix) with ESMTP id 89D7741A0A; Wed, 4 Jun 2025 01:03:48 +0000 (UTC) Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists1.osuosl.org (Postfix) with ESMTP id C8C70DA for ; Wed, 4 Jun 2025 01:03:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id C530C419CA for ; Wed, 4 Jun 2025 01:03:46 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id Fv6VIv4DuOrw for ; Wed, 4 Jun 2025 01:03:46 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=172.105.4.254; helo=tor.source.kernel.org; envelope-from=sashal@kernel.org; receiver= DMARC-Filter: OpenDMARC Filter v1.4.2 smtp4.osuosl.org EBCBE419AB DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org EBCBE419AB Received: from tor.source.kernel.org (tor.source.kernel.org [172.105.4.254]) by smtp4.osuosl.org (Postfix) with ESMTPS id EBCBE419AB for ; Wed, 4 Jun 2025 01:03:45 +0000 (UTC) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id F2628629D1; Wed, 4 Jun 2025 01:03:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83625C4CEF3; Wed, 4 Jun 2025 01:03:43 +0000 (UTC) From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Kyungwook Boo , Przemek Kitszel , Simon Horman , Aleksandr Loktionov , Rinitha S , Tony Nguyen , Sasha Levin , intel-wired-lan@lists.osuosl.org Date: Tue, 3 Jun 2025 21:02:03 -0400 Message-Id: <20250604010213.3462-52-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250604010213.3462-1-sashal@kernel.org> References: <20250604010213.3462-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.6.92 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1748999024; bh=+lDSaCO3yDXXZ35T33xTthIJWhWAw5s/bmcQcKv1Eg8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=NvHMJ3QvYyVykYuwER2bysu8Hbc95xVfcdHrXNkgrOts9hA2tj75VB1JUA/ySZcSW UYULmmRGywrY30Vh/zTYc0fEnlqBJI7/MtPAdjFd3G/w0M+HDTX6LmHxuDwh0fiLl2 2pNu+P136Igt1KiBe1QmeAYQ6LzIJxJKVGXhZu2ZfE7YVdldLeTPS5JT6yKni+tHj8 /CBGnsEER/ZQ3r5tlkXmU6wmbYASnGA9bs1m18Y0AiKk7y2Ev1fwJ6tu/PogTqfKM8 Ax2j1Bz7rlCRdC6nDBxB31yPwx7FCtGzPGDtA2550ivOPAi2lva39u1cIKQs9Ig5Wg RfDBtg9kSouTg== X-Mailman-Original-Authentication-Results: smtp4.osuosl.org; dmarc=pass (p=quarantine dis=none) header.from=kernel.org X-Mailman-Original-Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=NvHMJ3Qv Subject: [Intel-wired-lan] [PATCH AUTOSEL 6.6 52/62] i40e: fix MMIO write access to an invalid page in i40e_clear_hw X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" From: Kyungwook Boo [ Upstream commit 015bac5daca978448f2671478c553ce1f300c21e ] When the device sends a specific input, an integer underflow can occur, leading to MMIO write access to an invalid page. Prevent the integer underflow by changing the type of related variables. Signed-off-by: Kyungwook Boo Link: https://lore.kernel.org/lkml/ffc91764-1142-4ba2-91b6-8c773f6f7095@gmail.com/T/ Reviewed-by: Przemek Kitszel Reviewed-by: Simon Horman Reviewed-by: Aleksandr Loktionov Tested-by: Rinitha S (A Contingent worker at Intel) Signed-off-by: Tony Nguyen Signed-off-by: Sasha Levin --- **YES** This commit should be backported to stable kernel trees. Here's my extensive analysis: ## Analysis of Code Changes The commit changes variable types in `i40e_clear_hw()` from unsigned (`u32`) to signed (`s32`) for: 1. `num_pf_int` - number of PF interrupts 2. `num_vf_int` - number of VF interrupts 3. `i` - loop counter variable **Critical Security Issue**: The problem occurs when hardware registers contain malicious values where `num_pf_int` or `num_vf_int` could be 0 or 1. In the loops at lines 852-853 and 858-859: ```c for (i = 0; i < num_pf_int - 2; i++) wr32(hw, I40E_PFINT_DYN_CTLN(i), val); ``` If `num_pf_int` is 0 or 1, then `num_pf_int - 2` becomes a large positive number due to unsigned integer underflow (0xFFFFFFFE or 0xFFFFFFFF), causing the loop to iterate billions of times and write to invalid MMIO addresses, leading to system crashes or potential security vulnerabilities. ## Comparison with Similar Commits This fix follows the **exact same pattern** as Similar Commit #2 (fc6f716a5069), which was marked **YES** for backporting. That commit addressed the same class of vulnerability in the same function: - **Similar Commit #2**: Added bounds checking (`j >= base_queue`, `j >= i`) to prevent underflow in queue/VF calculations - **Current Commit**: Changes variable types to signed to prevent underflow in interrupt calculations Both fixes address **integer underflow vulnerabilities in `i40e_clear_hw()`** that can lead to **MMIO writes to invalid memory pages**. ## Backport Suitability Criteria ✅ **Fixes important security bug**: Prevents system crashes and potential memory corruption ✅ **Small, contained change**: Only changes variable types, no logic changes ✅ **Minimal side effects**: Type changes are safe and don't affect functionality ✅ **No architectural changes**: Simple type fix ✅ **Critical subsystem**: Network driver, but change is isolated ✅ **Clear commit message**: Explicitly describes the security issue ✅ **Follows stable rules**: Important security bugfix with minimal risk ## Historical Context The vulnerability was introduced in commit 838d41d92a90 ("i40e: clear all queues and interrupts") from 2014. A related fix (fc6f716a5069) was already applied for similar underflow issues in the same function and was backported. This commit completes the fix by addressing the remaining underflow vectors. ## Risk Assessment **Risk: MINIMAL** - This is a simple type change that: - Makes signed arithmetic behave correctly - Prevents undefined behavior from unsigned underflow - Has no functional impact on normal operation - Only affects error conditions with malformed hardware registers The fix is **essential for security** and has **virtually zero regression risk**, making it an ideal candidate for stable backporting. drivers/net/ethernet/intel/i40e/i40e_common.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/net/ethernet/intel/i40e/i40e_common.c b/drivers/net/ethernet/intel/i40e/i40e_common.c index 4d7caa1199719..5d46a8e5376da 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_common.c +++ b/drivers/net/ethernet/intel/i40e/i40e_common.c @@ -1067,10 +1067,11 @@ int i40e_pf_reset(struct i40e_hw *hw) void i40e_clear_hw(struct i40e_hw *hw) { u32 num_queues, base_queue; - u32 num_pf_int; - u32 num_vf_int; + s32 num_pf_int; + s32 num_vf_int; u32 num_vfs; - u32 i, j; + s32 i; + u32 j; u32 val; u32 eol = 0x7ff; -- 2.39.5 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 C561264A98; Wed, 4 Jun 2025 01:03:44 +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=1748999024; cv=none; b=CyCB8KBqA2rGLAsPRpvGlcvJzFKLbFte8MnDc1gvqGhSUTgjyRErc9u/VvgJN39WWJBksjepHMmOm6rIZuaUH+csJ4p4jTRs1F/7XyU52xSiXBei5sRh6Ku7te/2086sMJ5KPi9kQE7fBeQi7ggI85kUPkcPPlgPcwid779t/B0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1748999024; c=relaxed/simple; bh=+lDSaCO3yDXXZ35T33xTthIJWhWAw5s/bmcQcKv1Eg8=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=bDFx2Ya41Jl8tREVJBaBPa6hEZoU5tVY5y6ee5rLzILvdMFdbeBo1Gfj3vZswLEdDx8NBS6bonNbZmsJ5pCQ3UnXQOSz5NPOs0mdU6TZbuNA/faKuHFej0M08GcMP0C5mxGlwDLK3WKetD6SUHLL9EvO1+DTy+0Z2shUqHwLlCY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NvHMJ3Qv; 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="NvHMJ3Qv" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83625C4CEF3; Wed, 4 Jun 2025 01:03:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1748999024; bh=+lDSaCO3yDXXZ35T33xTthIJWhWAw5s/bmcQcKv1Eg8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=NvHMJ3QvYyVykYuwER2bysu8Hbc95xVfcdHrXNkgrOts9hA2tj75VB1JUA/ySZcSW UYULmmRGywrY30Vh/zTYc0fEnlqBJI7/MtPAdjFd3G/w0M+HDTX6LmHxuDwh0fiLl2 2pNu+P136Igt1KiBe1QmeAYQ6LzIJxJKVGXhZu2ZfE7YVdldLeTPS5JT6yKni+tHj8 /CBGnsEER/ZQ3r5tlkXmU6wmbYASnGA9bs1m18Y0AiKk7y2Ev1fwJ6tu/PogTqfKM8 Ax2j1Bz7rlCRdC6nDBxB31yPwx7FCtGzPGDtA2550ivOPAi2lva39u1cIKQs9Ig5Wg RfDBtg9kSouTg== From: Sasha Levin To: patches@lists.linux.dev, stable@vger.kernel.org Cc: Kyungwook Boo , Przemek Kitszel , Simon Horman , Aleksandr Loktionov , Rinitha S , Tony Nguyen , Sasha Levin , intel-wired-lan@lists.osuosl.org Subject: [PATCH AUTOSEL 6.6 52/62] i40e: fix MMIO write access to an invalid page in i40e_clear_hw Date: Tue, 3 Jun 2025 21:02:03 -0400 Message-Id: <20250604010213.3462-52-sashal@kernel.org> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250604010213.3462-1-sashal@kernel.org> References: <20250604010213.3462-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.6.92 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Kyungwook Boo [ Upstream commit 015bac5daca978448f2671478c553ce1f300c21e ] When the device sends a specific input, an integer underflow can occur, leading to MMIO write access to an invalid page. Prevent the integer underflow by changing the type of related variables. Signed-off-by: Kyungwook Boo Link: https://lore.kernel.org/lkml/ffc91764-1142-4ba2-91b6-8c773f6f7095@gmail.com/T/ Reviewed-by: Przemek Kitszel Reviewed-by: Simon Horman Reviewed-by: Aleksandr Loktionov Tested-by: Rinitha S (A Contingent worker at Intel) Signed-off-by: Tony Nguyen Signed-off-by: Sasha Levin --- **YES** This commit should be backported to stable kernel trees. Here's my extensive analysis: ## Analysis of Code Changes The commit changes variable types in `i40e_clear_hw()` from unsigned (`u32`) to signed (`s32`) for: 1. `num_pf_int` - number of PF interrupts 2. `num_vf_int` - number of VF interrupts 3. `i` - loop counter variable **Critical Security Issue**: The problem occurs when hardware registers contain malicious values where `num_pf_int` or `num_vf_int` could be 0 or 1. In the loops at lines 852-853 and 858-859: ```c for (i = 0; i < num_pf_int - 2; i++) wr32(hw, I40E_PFINT_DYN_CTLN(i), val); ``` If `num_pf_int` is 0 or 1, then `num_pf_int - 2` becomes a large positive number due to unsigned integer underflow (0xFFFFFFFE or 0xFFFFFFFF), causing the loop to iterate billions of times and write to invalid MMIO addresses, leading to system crashes or potential security vulnerabilities. ## Comparison with Similar Commits This fix follows the **exact same pattern** as Similar Commit #2 (fc6f716a5069), which was marked **YES** for backporting. That commit addressed the same class of vulnerability in the same function: - **Similar Commit #2**: Added bounds checking (`j >= base_queue`, `j >= i`) to prevent underflow in queue/VF calculations - **Current Commit**: Changes variable types to signed to prevent underflow in interrupt calculations Both fixes address **integer underflow vulnerabilities in `i40e_clear_hw()`** that can lead to **MMIO writes to invalid memory pages**. ## Backport Suitability Criteria ✅ **Fixes important security bug**: Prevents system crashes and potential memory corruption ✅ **Small, contained change**: Only changes variable types, no logic changes ✅ **Minimal side effects**: Type changes are safe and don't affect functionality ✅ **No architectural changes**: Simple type fix ✅ **Critical subsystem**: Network driver, but change is isolated ✅ **Clear commit message**: Explicitly describes the security issue ✅ **Follows stable rules**: Important security bugfix with minimal risk ## Historical Context The vulnerability was introduced in commit 838d41d92a90 ("i40e: clear all queues and interrupts") from 2014. A related fix (fc6f716a5069) was already applied for similar underflow issues in the same function and was backported. This commit completes the fix by addressing the remaining underflow vectors. ## Risk Assessment **Risk: MINIMAL** - This is a simple type change that: - Makes signed arithmetic behave correctly - Prevents undefined behavior from unsigned underflow - Has no functional impact on normal operation - Only affects error conditions with malformed hardware registers The fix is **essential for security** and has **virtually zero regression risk**, making it an ideal candidate for stable backporting. drivers/net/ethernet/intel/i40e/i40e_common.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/net/ethernet/intel/i40e/i40e_common.c b/drivers/net/ethernet/intel/i40e/i40e_common.c index 4d7caa1199719..5d46a8e5376da 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_common.c +++ b/drivers/net/ethernet/intel/i40e/i40e_common.c @@ -1067,10 +1067,11 @@ int i40e_pf_reset(struct i40e_hw *hw) void i40e_clear_hw(struct i40e_hw *hw) { u32 num_queues, base_queue; - u32 num_pf_int; - u32 num_vf_int; + s32 num_pf_int; + s32 num_vf_int; u32 num_vfs; - u32 i, j; + s32 i; + u32 j; u32 val; u32 eol = 0x7ff; -- 2.39.5