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 55248490BE7 for ; Fri, 25 Sep 2026 10:26:30 +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=1790331991; cv=none; b=pIfXmShr2CxinoqYY51Wo2ra1oQa0AsLXtcXY3PWSCAXQ9smIxivAi6Ms9xGDU0XngImj136mTLemKohha6FsvRHFYXSVQ1rNaIo2ZyAnN62pEP4SYbh5T3ZurdxKLi1cODvmiyz4xi0q1147phAnnSxiQ1z8qdGP9D7EbxX22U= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790331991; c=relaxed/simple; bh=tAfXjWY68XsMVDRu3340hd+veTxaoBdTfYym9MDcxxg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=RHMc94ctojsowUHbHK4AER6laOcUKIQauKBzTpv+sRiSCXcpOHw0BI7pzeg1UnCjSiGwUgPybburPfYMYM/EskiQ8uTBnOkSjeN70cYEOCYaDDzJgUEjd2jfd7fzhcKQVjaDESK+Ueprq9t4zWNCqQD0uj3qr9VMMoKTLAqCVww= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Xk3nqfwT; 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="Xk3nqfwT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9157F1F000FF; Fri, 25 Sep 2026 10:26:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1790331990; bh=k4rtIkgSINaefcY97AihMm1dQLL7IEEGg5sdNiU1qMw=; h=From:To:Cc:Subject:Date:Reply-To; b=Xk3nqfwT7mBvmPV3zRJCRi8UQv4vFIcJaJ+i2qrdERpkCMxLi7ZRym1b5Q5zrGmvQ Wq1C+vR+U8By1x1dSBOW4JjOYnx/UP+ULqXRAZAtR1QxsQMnzKFOJJy68tk48o8kq/ SHvr25Y5l5Uwuey2pvd3XsFwGLap2m4zRu5gNUo8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-97603: idpf: disable DIM work before freeing q_vectors Date: Fri, 25 Sep 2026 12:23:03 +0200 Message-ID: <2026092500-CVE-2026-97603-d993@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=3949; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Y6KEt6nGOipOGsQdGBg9rSSzM8V8uWElz7Dnyu31Nlc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFnbvD0uGK99GXf1qHpn2o0Pyl+5+J+dztX/1awj+vy0b 9Gvv/uMO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAii2oYFpxcnczz5dHJeptW LeUf156WXDl6o4VhwZHdIY/1VRQcJ2h5ybG/v7UsxuGSFgA= 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: idpf: disable DIM work before freeing q_vectors idpf never drains the Tx/Rx DIM works before freeing the memory they live in. tx_dim and rx_dim are embedded in struct idpf_q_vector, they are queued from the NAPI poll via net_dim(), and idpf_vport_intr_rel() ends with kfree(rsrc->q_vectors). Nothing in the driver cancels them. idpf_tx_dim_work() and idpf_rx_dim_work() then run on freed memory: idpf_vport_intr_write_itr() writes the ITR register through q_vector->intr_reg.tx_itr / rx_itr, void __iomem pointers loaded out of the freed q_vector. No configuration is needed to get there -- IDPF_ITR_IS_DYNAMIC() is defined as (itr_mode) and idpf_vport_alloc() initialises both modes to IDPF_ITR_DYNAMIC. Draining after idpf_vport_intr_napi_dis_all() is not enough on its own. idpf_net_dim() is called from inside the "if (napi_complete_done(napi, work_done))" branch of the poll, and napi_complete_done() has already cleared NAPIF_STATE_SCHED by then. napi_disable_locked() waits only while (val & (NAPIF_STATE_SCHED | NAPIF_STATE_NPSVC)), so napi_disable() can return while the poll tail is still queueing the work, and a plain cancel_work_sync() would be re-armed behind the drain. Use disable_work_sync(): schedule_work() on a work with a non-zero disable count is dropped by clear_pending_if_disabled() before __queue_work() is reached. Move idpf_init_dim() to idpf_vport_intr_alloc() so the works are initialised on every path that can reach the drain -- the three "goto intr_deinit" sites between idpf_vport_intr_init() and idpf_vport_intr_ena() get there without the enable side having run. Nothing re-enables them: rsrc->q_vectors is freed on every exit from idpf_vport_open() and on every idpf_vport_stop(), so the count dies with the object. It is a race, not a deterministic failure -- net_dim() only schedules once DIM_NEVENTS events have accumulated and the profile index changes. A KASAN ifup/ifdown loop under load is the way to see it. The Linux kernel CVE team has assigned CVE-2026-97603 to this issue. Affected and fixed versions =========================== Issue introduced in 6.7 with commit c2d548cad1508d334517bcbd7cd5c915cc831fc0 and fixed in 6.18.53 with commit 7e4312953788244d47074987d40d76702cf929f1 Issue introduced in 6.7 with commit c2d548cad1508d334517bcbd7cd5c915cc831fc0 and fixed in 7.2.7 with commit cd7a1598645b6917a8676b7e2efe8d97ce68a952 Issue introduced in 6.7 with commit c2d548cad1508d334517bcbd7cd5c915cc831fc0 and fixed in 7.3-rc3 with commit 7dd4c829bac2916be98a3e34b41daaba7f42b4c4 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-97603 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/intel/idpf/idpf_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/7e4312953788244d47074987d40d76702cf929f1 https://git.kernel.org/stable/c/cd7a1598645b6917a8676b7e2efe8d97ce68a952 https://git.kernel.org/stable/c/7dd4c829bac2916be98a3e34b41daaba7f42b4c4