From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154543; b=A19TtBP9E72odfAGFTDBtM641w4eWaO0MaPfysnaxlz1snSsBbO8QJ8pdPwtjvg2Dvs1 abx1qAneUQmlSxHmetaInVQWPVdGmhrLYkoT5FHU67C4vXunUMfJORtjtquaxjWuLa9/Q Fhkcqws9Cw4BRYRp6KR5Ub/dpXSUmMxvWUflV/Ak36IKv5pv1ZpXTBxk5dHWrOXAFgpKE Y/8g2KeP0+rwIsUcgwloWcxtABNRlsAFW1MrYg3EDbR8hwiLmlyiFP4SX9RYKc1sRUD2P rZwG2lEQUuxN24/jdstldLsb6YKozwoOYQd7aGu4hteXgTugRfsr9vliu78owgww1fA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154543; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=eAXY7a6YNbSpwpFP7RBkMThZyB413E4b2EC33kH28hY=; b=vr+lp/qB+qxOXGX5DhCfRKGYdB/tVUAF8YSMCZQHfAhbEp6upTNIunPaQRg/kOlB4kCf bPibyTknth1JnwmWmmEx2hzmuPR6Ow3Of6rm7mPuQuviq6g8svAmvvfuFRmbBKl3fPGby WG57A7JHmGuf1sz9CSyVrdR+7RAKbmMSv2flyMTPTvp77PQtAPwj6dJ56OzJHDsLz5O12 gnGxg96GIxM4huDfH/kuo/Bdj5coW1awo4xw4tvIq9qUkjN/K1ps/InFL0QwnehejisT2 AJmwHuxQ7LeapKVu0xCxsutE4J9Rhuib9k3FwoFw3+drGKU7ntfXVSATk9x/7UXkGxQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=ZxUHBWPn; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4DB0E606A525 for ; Fri, 20 Nov 2026 06:02:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=ZxUHBWPn Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9E9651F000CF; Fri, 20 Nov 2026 06:02:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154543; bh=eAXY7a6YNbSpwpFP7RBkMThZyB413E4b2EC33kH28hY=; h=From:To:Cc:Subject:Date:Reply-To; b=ZxUHBWPnDTsHt1GpHA266meQz+jUd2oxDAdcvjQfP8XelFBLPg6yE8u4hM4H1kvOL qM6hQn0O59pQ+qAPTe4igEAg91ZQehVLvmxaD0yHPAewEg6dMPsgKaacQTjoDBhqSW eesbe68C1ZpXHMyITpFtdJyBwgIAI+KhcGf6VoHg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99780: net/9p/usbg: always reset completion when disconnecting Date: Fri, 20 Nov 2026 06:52:46 +0100 Message-ID: <2026112031-CVE-2026-99780-cdc7@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2470; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6J/Hy4ewDV+HeXUsJlkWffVsKGL4CFua6zwTInTBPP8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y9PkpzSwX6w72P37rVzBfZmisqev3J6/eTkZZff8 d17/ejFu45YFgZBJgZZMUWWL9t4ju6vOKToZWh7GmYOKxPIEAYuTgGYyMxuhnm6a1YKqWqxZ9cc ldRJOnG/NaHxgifDPO2lJQuP6ig4OPotEM4I5V2yX9nqIwA= 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/9p/usbg: always reset completion when disconnecting When some tx or rx transfers were pending while closing the connection, the completion handler could catch one pending completion call. To ensure a normal start when mounting again, we have to reset the completion and flush any pending completions. The Linux kernel CVE team has assigned CVE-2026-99780 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.12.118 with commit ec4fbfe4f33318f3d081c879e50fb66b9b1304e3 Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.18.64 with commit a3a82145d7b382badc16eea965d129a3e9e68e3d Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.3.5 with commit 56a679b49c0598ec0d051b0f592c978fdc77f5a6 Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.4-rc2 with commit 08c6b9f484a406d9d87c5b2580725d2e0597f3b9 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-99780 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/9p/trans_usbg.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/ec4fbfe4f33318f3d081c879e50fb66b9b1304e3 https://git.kernel.org/stable/c/a3a82145d7b382badc16eea965d129a3e9e68e3d https://git.kernel.org/stable/c/56a679b49c0598ec0d051b0f592c978fdc77f5a6 https://git.kernel.org/stable/c/08c6b9f484a406d9d87c5b2580725d2e0597f3b9