From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 ACF7857EDA9 for ; Fri, 11 Sep 2026 19:48:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156135; cv=none; b=Nx9EdtfvN546188oqisLht4rKT8apc78evHSeK2d/rh5akM8DPH4pMffnJnUhML50n7o+/85lWi0oXxJI6/GhLD6VIV6u8Ap0ZuhJ5TxIUAp5HAy9Mck5lIhQxgEViKTUJZ4hF/WM9c4f+2iR6rvNkhK7XIzudJPJwA62Z90GK0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156135; c=relaxed/simple; bh=pXOND/edw99+LcLbDDLI4TfQdnE77r+PLBKCfcS0iKE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=NYJj7+zOtwEdabd+t5tgA7wsN0Ih3Lte83IyrgH9dmhTbsMrCe4V4P4pJGFYc3wSdXgDOvP2LieNks1WrnIzC7zhpI1h6Fv/SVQ9lvwmzWDGe7szcJPP6V7AdtCk4Y0ZApcYTz6GUoAxz7tLkH0XIHFK6cT667/VOAaxhzVUspk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=EixWbygB; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="EixWbygB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BF2A61F0089F; Fri, 11 Sep 2026 19:48:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156130; bh=BBI9Gw+UoUROw0cGpcvP7xIxEbhzohcN0Tyhy48XHwk=; h=From:To:Cc:Subject:Date:Reply-To; b=EixWbygBfYOF2DU5ywSYLhct3u1u/jibm55wVSe/6B/JpUgbnlKKdKqouP5Hxe9IJ FSk6sCprHAsjLqN7IaSH5lYfJtzYxTeQplxKSMewwLq33u1Y1pg9j9oOGcmiypMT/S yCu9yWPOcIlJptOQCXchyHTFRtnF68s/uf9NwZr4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80998: net: bnxt: ring the doorbell when SW USO exits early Date: Fri, 11 Sep 2026 21:41:44 +0200 Message-ID: <2026091150-CVE-2026-80998-78c5@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2794; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=j4PkHFxCzceMlHNgXGhckTYbvGd20ZJQJKRntLrbSag=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIp1m/0oRu3wrbeukJy0GVx6GSKinztuzxzfz5MXKj MOyR5jnd8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEhH8xzC/Z4xoze0I/67VF 8rVM2053zTaxyWeYnxVpdj3i6l03mRy1CIadt/yVjF+vBAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: net: bnxt: ring the doorbell when SW USO exits early When a burst of packets is handed down to the driver, the driver defers the doorbell to the end by setting txr->kick_pending = 1. The normal TX path handles this, but the SW USO path can miss it if it returns early. If bnxt_sw_udp_gso_xmit runs but returns early with NETDEV_TX_BUSY and txr->kick_pending was previously set to 1, then the TX queue can stall because the driver wrote some BDs but never wrote the doorbell. The device won't know to do the TX which would generate the completion that would wake the queue back up. Simplify bnxt_sw_udp_gso_xmit to set txr->kick_pending in its success case and check the flag on return. The added check after bnxt_sw_udp_gso_xmit returns ensures that any pending doorbells are written handling both successful USO and any early returns, which prevents the TX queue stall mentioned above. This TX queue stall was observed on a production system with a netdev TX watchdog informing about the queue stall. The Linux kernel CVE team has assigned CVE-2026-80998 to this issue. Affected and fixed versions =========================== Issue introduced in 7.1 with commit cc5d90667db81474ed7a92a1b2fa3daec5559307 and fixed in 7.2.4 with commit 48d1c9665db6e3d4aeca62eb669377162ebc6fdf Issue introduced in 7.1 with commit cc5d90667db81474ed7a92a1b2fa3daec5559307 and fixed in 7.3-rc1 with commit 4e15e89faac9f308baeb01f46c13a051814d2449 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-80998 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/ethernet/broadcom/bnxt/bnxt.c drivers/net/ethernet/broadcom/bnxt/bnxt_gso.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/48d1c9665db6e3d4aeca62eb669377162ebc6fdf https://git.kernel.org/stable/c/4e15e89faac9f308baeb01f46c13a051814d2449