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 D983F4DEC3E for ; Thu, 17 Sep 2026 16:14:59 +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=1789661701; cv=none; b=DQ3pkvBbiEPKTt0/WAsFleqq9jmoE5PwksztnriU5/zWs8/0bbEA6rmp4CjrRodgrb+fbJFyrv+YNshhUSOnU2uNLlPFNsqae2uyfBuiiy9zZ88+DaPn1At1crnlS0Boo4BkJY64rcZ07GhEUnTDIjAM+fIPCOoiKK/kkxOWqZE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789661701; c=relaxed/simple; bh=darEzE7oFZNBAWPAW9DKkpvG4Y756MtFiC+9O9NwzQA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ACC5YczWmSfxf3fBoqT1y1pIZnT9mTVxy8ug0kMbmVt0c+Fz0zV4TxGC46Hj/7xJCTqYpMYd5aalOCzdWMyDeD0N17Yf3UlAizlTtPOBqsqPt3SvLVIpMyDhYG/k0XtuNNB5BxATEVcTgFXMEnm4myUElhhXu+A3SWefI+gErAg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=jnp5o2vX; 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="jnp5o2vX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DFE131F000FF; Thu, 17 Sep 2026 16:14:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789661699; bh=lyNXum0oDsR9Y1jsS1HZFphwaAtpyNy8y9vBI8RHJKM=; h=From:To:Cc:Subject:Date:Reply-To; b=jnp5o2vX1JULuVVPf+GDzqr8nShbgtJsveCSgwPFC/SPoJ4xlfk/QX6HYuUiwQCtH IiBRcZFePPeLWdqazlKZvOJ4o5HXX13VW9SbJnhzdoSk2LXLwrlZKzU72xSiF4SB9+ 7M4YaP6IYZO1O3RKXDAfdVtkZ055CrYGv/DSEYYQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-90107: net/smc: free pending qentry in smc_llc_flow_stop() before memset Date: Thu, 17 Sep 2026 17:08:57 +0100 Message-ID: <2026091714-CVE-2026-90107-eaf8@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=4097; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Kb459Sh1yboRsuMvDv2/OeSvVWlXkMIUlbtmdS7qRl0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBPI+3BEwO5BkciNM+Wgop3Epk3XMeYOEGP3SN4Ecl xY7xv7oiGVhEGRikBVTZPmyjefo/opDil6Gtqdh5rAygQxh4OIUgIl0TGJYcLpUQ/142hm9W/vD by/d3rDvzXWN/wzztBpZ+9/ylTOacybwtKZ8bjAUKzQHAA== 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/smc: free pending qentry in smc_llc_flow_stop() before memset smc_llc_flow_stop() resets a flow struct with a blind memset: spin_lock_bh(&lgr->llc_flow_lock); memset(flow, 0, sizeof(*flow)); flow->type = SMC_LLC_FLOW_NONE; spin_unlock_bh(&lgr->llc_flow_lock); If flow->qentry is non-NULL at this point the pointer is overwritten without the allocation being freed, leaking one kmalloc object. A late-arriving duplicate CONFIRM_LINK or ADD_LINK_CONT message can set flow->qentry after the legitimate message has been consumed by the waiter via smc_llc_flow_qentry_clr() (which NULLs the pointer but leaves flow->type non-zero) but before the flow completes and smc_llc_flow_stop() runs. In that window the duplicate is stashed into flow->qentry, and then lost when smc_llc_flow_stop() zeros the struct. Call smc_llc_flow_qentry_del() inside the lock before the memset. smc_llc_flow_qentry_del() already checks flow->qentry before freeing, so the normal case where no entry is pending is a no-op. The Linux kernel CVE team has assigned CVE-2026-90107 to this issue. Affected and fixed versions =========================== Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 5.10.270 with commit 8e3deb150a5237b672c4579e69a6deb02027dbed Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 5.15.221 with commit 11bc373ee6630709f0c2da2e7860c23d503c9e9d Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 6.1.188 with commit 032aec7d03c9102616b98fea74f8f7145e7f867c Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 6.6.157 with commit 957dba2b8b5aebfe09caa6a6b22b958079082eab Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 6.12.110 with commit f03aa5d36ae3c4068a1c3885146be99aa7fd9307 Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 6.18.52 with commit 0879ea157acc1ac6752f6fcb755d1f91a2359238 Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 7.2.6 with commit 5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b Issue introduced in 5.8 with commit 555da9af827d95134656fa459c8f3ece04dd867a and fixed in 7.3-rc1 with commit 5ee0ceddc7785c6dcf4a8107fef01f0414a354f4 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-90107 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: net/smc/smc_llc.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/8e3deb150a5237b672c4579e69a6deb02027dbed https://git.kernel.org/stable/c/11bc373ee6630709f0c2da2e7860c23d503c9e9d https://git.kernel.org/stable/c/032aec7d03c9102616b98fea74f8f7145e7f867c https://git.kernel.org/stable/c/957dba2b8b5aebfe09caa6a6b22b958079082eab https://git.kernel.org/stable/c/f03aa5d36ae3c4068a1c3885146be99aa7fd9307 https://git.kernel.org/stable/c/0879ea157acc1ac6752f6fcb755d1f91a2359238 https://git.kernel.org/stable/c/5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b https://git.kernel.org/stable/c/5ee0ceddc7785c6dcf4a8107fef01f0414a354f4