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 A3A2B389106 for ; Sun, 18 Oct 2026 15:34:05 +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=1792337646; cv=none; b=G5U/PYqBgcPQUQR8lkvf440v6MdQvU23eI5zFNflo/1W9b3+gRHh02IGfdd6zsTEfy65qRMvex/tuePUMxuoWIWrLTIP3anmki9hUtlPzAp++0fnblCAleHWEaHCSl3Icq93lZn8e3IqkhCOYTURZ5Mkyl78D8rWmzXUr31DSoM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792337646; c=relaxed/simple; bh=/Wt+6CdFnY1/HV42ELPf9TXhmXX6vpP6xxWyu4M3dfo=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=VCt8bIxiclXL7NlSDwPWSQGLRbyYWaFqCCetrBNQIuZVHsAGqYYyPT2RmVIOm4H91/ScnMveYG4gQoX3mPS849EvYaXwGZwFBG05+oVZ2D0bFHZZvBidGlJYYWl+J08hJQGc+UrKGBiGBOsW6bBQD/qm9nTVND6fsu1MvFBP9/0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=DYeObT+F; 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="DYeObT+F" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 96C0E1F000C4; Sun, 18 Oct 2026 15:34:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792337645; bh=y0UiZTwGgeHDA+CelnFEOj7nrCdytpmS5pJdEU5LS7Q=; h=From:To:Cc:Subject:Date:Reply-To; b=DYeObT+FBeLUkyaVZK4bN4g5IUZd5zbbf17fsbhiXHv6fKe3UXvWizgRtwdqLviSA I01nyWJ+/x4xfl4pQT2ucpt1ipRFmCuMCSuFLG1ei7c+5T1wsRBEcVVsK28cuFLwpD s7ssdyP6UAFRgIDCVC/8tlwwNb8zZHUG3ufXGrBg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98617: eth: fbnic: use the Rx queue napi pointer to find the napi vector Date: Sun, 18 Oct 2026 17:18:01 +0200 Message-ID: <2026101841-CVE-2026-98617-894e@gregkh> X-Mailer: git-send-email 2.56.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=3252; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6hm1ShQUxO2Ow5gzjx6GhIoUzinqWnwyLIqBsNfCjxY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXHs3dcdbdbNrOSXeLky9FJMVcDP0le3ba5od+gjNT9 Lkylr7Z2RHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATuVXAML9y9qzktZUS+X9W Pbc5aPH7c/99Vw6GBUenvlJWW1RvMI2lon5KfdAaJlUeHgA= 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: eth: fbnic: use the Rx queue napi pointer to find the napi vector The queue management ndos pick the napi vector for an Rx queue with: nv = fbn->napi[idx % fbn->num_napi]; The issue is this is only correct in the cases where there are no standalone Tx vectors. In those cases we were allocating the Tx vectors first and then the Rx so the queues would be pointing to Tx NAPI vectors instead of the Rx ones. The mapping the ndos want is already recorded. fbnic_set_netif_napi() publishes it with netif_queue_set_napi(), which stores the napi pointer in netdev_rx_queue.napi, and fbnic_reset_netif_napi() clears it again. Both run under the netdev instance lock that the queue management ndos also hold, so the pointer can be read directly. Use it and drop the divide. The pointer is NULL exactly while the datapath is down, so fbnic_queue_mem_alloc() can reject that case rather than reaching into freed state: netdev_rx_queue_restart() calls it before it tests netif_running(), and fbnic_pm_suspend() leaves netif_running() true across a PCIe recovery that never completes, so a queue restart can arrive after fbnic_stop() has freed the rings and the vectors. fbnic_stop() clears the association in fbnic_reset_netif_queues() before fbnic_free_napi_vectors(), so the NULL is always published first. fbnic_queue_start() and fbnic_queue_stop() need no check of their own, as netdev_rx_queue_reconfig() only reaches them once fbnic_queue_mem_alloc() has succeeded under the same instance lock. The Linux kernel CVE team has assigned CVE-2026-98617 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18 with commit da43127a8edc7498cce7b2554533f4027c618933 and fixed in 7.2.9 with commit 1fb569cf3bf97e552f465b2c719e36b48ae7c18b Issue introduced in 6.18 with commit da43127a8edc7498cce7b2554533f4027c618933 and fixed in 7.3-rc5 with commit b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e 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-98617 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/meta/fbnic/fbnic_txrx.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/1fb569cf3bf97e552f465b2c719e36b48ae7c18b https://git.kernel.org/stable/c/b5d9e9d4d0c13bc8b60d8d97e7a07fb25fea639e