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=1795154531; b=HY4Bpfsb3m/r5sfkBl0PGfNLnA7n2qZaYtDOyh+v4hGeGqlUpZQLAzV40BAn25vuAjUm oRazFm8V1+rCSSkD+fPMJ876WZbWThy+mT3KU1bQm26IKczlG0EG4F0d3K2t4XEVKLnXw BBhPNISB2EL/+POzwC2SnHPkYvW9YUjLxcno7qV9S/EuR+lO2ONcnvNpKnOKIxrDmNC6Z xmiIhUZIUaukIReMOkdpziJ5nY2oiTrXM79umKbkhR/G0mTI2RQay1lpmSf6tQ2lCrrfn eYb0qd36t5esj41EWgMj8Jc5PeP9YbVDhTdmEge9q6cr4gml5iF3YAkmyWxtCO6vXTA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154531; 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=A9sMjpkYoBHuzJ0MlGL67CFbbdwCaE7iB5koQ+LNCkI=; b=BB3K+4GASjzcrqQ9pWpboBgjFUrf7io0EpdB+wvnV4K9gAlzlAYjZaCHfT2kSQUe29T8 KHNUSlS00J3TO1jCTtfpF76L1PCbh5IkYHaOh7oULRFCZ64qgwx5P4F6ujZtY6/1uPbPb l4Zon3gG1U/pp4W2pjGR/3vMw11fSPy+Sm80o5ZMk2qB/odIm+BDsNqgMp9Enm6hX/E3Z MlOAmHQPeeB+ve1ntxNbwuBGGisPKaWuobMlZ3Q8Jpvv7V0smE61XUsp9RQWHNpTgHdgM aVp6S7rpNr2tGi+l7xPntvRvfkLPdfVscbsI4uKr1NL/EHDOvLVk9vXoIcF/oIYVGPA== 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=OMpSDcd5; 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 CFB99606A333 for ; Fri, 20 Nov 2026 06:02:11 +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=OMpSDcd5 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 29D251F000C6; Fri, 20 Nov 2026 06:02:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154531; bh=A9sMjpkYoBHuzJ0MlGL67CFbbdwCaE7iB5koQ+LNCkI=; h=From:To:Cc:Subject:Date:Reply-To; b=OMpSDcd5X9/Wkno3W3dA4/t9tEjWjj5jjTvdsGtAnCin2MiGAbJjlsQ02zjozIpdE ow12rmi4HwAjWpeYfZL3Cg6z5PTRhOfMLP0f2qGTOk97SxBARf188gU8u++E1FcIbI +q2cKdwX9FuhzEGYn2JTgEO3X2zwNkrLuKRSiTxY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99776: net/9p/usbg: clear stale client pointer on close Date: Fri, 20 Nov 2026 06:52:42 +0100 Message-ID: <2026112030-CVE-2026-99776-6ffa@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=2742; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=p5UwRPAh4EddftxnUnDLGd4IN5DTGnaCvy8fIEr8LAg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y9r+XhRJER0k9X2cinfTWzar2Ny12de03zqonBy5 au5+QbLOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAijuwMCxa1bm1nMGr7oRL+ 2llrpt3Tr5d+XmaYw2kSbG9/9zVr6h8rva1TeFcozGyNBwA= 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: clear stale client pointer on close p9_usbg_close() tears down the client transport, but usb9pfs keeps using usb9pfs->client from asynchronous TX and RX completion handlers. A late completion can therefore dereference a client that has already been freed during mount teardown. Clear usb9pfs->client under usb9pfs->lock when closing the transport, detach any pending TX request from in_req->context, and make the TX/RX completion handlers bail out once the transport has been detached. This keeps late completions from touching a freed or rebound p9_client. The Linux kernel CVE team has assigned CVE-2026-99776 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.12.118 with commit e56ec7e03bec90050368b9bc268d1de098bb92bc Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.18.64 with commit 951a7562ecde301a30ded7305b61dd0e9784bee8 Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.3.5 with commit c090c95f747714999a3fdebafa07b663473b7b7b Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.4-rc2 with commit a478958f4c1181ff3362f8857b489c2d069f9c7d 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-99776 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/e56ec7e03bec90050368b9bc268d1de098bb92bc https://git.kernel.org/stable/c/951a7562ecde301a30ded7305b61dd0e9784bee8 https://git.kernel.org/stable/c/c090c95f747714999a3fdebafa07b663473b7b7b https://git.kernel.org/stable/c/a478958f4c1181ff3362f8857b489c2d069f9c7d