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=1795154540; b=kdSSa6VeY0osrnw5vLnWhF8U+MOb656jkQaSrUbcF54XoYglRCDbAhD958VdV9S6PM02 niKYnz4nV7T2NODMElOki8oqG0m+3snhvqq0ue5ra83aSnEVmbT3aTdsHoqYuR9526Ft5 +ulCjoyKMom+p7YuyV1hnwVOM+1LNHRsA/LRN5YKEQAtbQVD9iWW6ziKnZO+o0CFua91t AMknSquSFsUZmInXU5UKrn/SyVtCiou0CxfDMUbA/F3ipGi0lwNk/TmB83hVQEfWUD9ou Wozm7d/mUrPeDBD3YRNVsOhb3aW7gX6jB2W3HnMZWZhnQpGbO360/9WZLbu3uCqXJ7A== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154540; 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=OBBDGRMeI69pzf5r7l+UciNfE0uZAyBQelOnY//jggg=; b=1/WE9mAffC53WivQeF+Ll2WxJmN0JlZUfR2CEI5YlGEB0RGINCvZ9tTD/vriX4Z2KdzT STOMugha72WkLIsL7Rh66W3pT59F7lXmU73hqCL4UhU7vOIm2Svq00F07T++hIxfAC/Kw LyPl/7LKpbjiLA3qEYmi+deMLxMqFNHlq5O0YkIwGSEOOdrLU3PZph+avNS0rn5dTvjT+ V4WnEl04fXH3feYl04RZvgx2XzRSoSW/FBLmmWslqTtWfD7/Sa/XT6+UVU1SW4QWlojqY fU8suWE+ymaSrhCaDIxwacmHqSJddYTZb9pg3wX2vjH9KUG2Zm3ohCmWBjipKMQ8LgA== 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=N7VzubYy; 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 76174606A504 for ; Fri, 20 Nov 2026 06:02:20 +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=N7VzubYy Received: by smtp.kernel.org (Postfix) with ESMTPSA id C3B661F000C6; Fri, 20 Nov 2026 06:02:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154540; bh=OBBDGRMeI69pzf5r7l+UciNfE0uZAyBQelOnY//jggg=; h=From:To:Cc:Subject:Date:Reply-To; b=N7VzubYyg+Yx085L1VtYCHNr/F9hxgoPXTyoc2cVq27PkuyCGaLAqhscsDzzWFXXS iTT7GHlNiBkVaSa9IJhCVwPpchsT1RspHWe7mhCKcoQ1Ubc7mX/TVrsJwpHHaNWuOl ARTPJNnh34GXCsak3RNhQwX2HmvY/WLZxGpBGstQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99779: net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable() Date: Fri, 20 Nov 2026 06:52:45 +0100 Message-ID: <2026112031-CVE-2026-99779-0718@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=3373; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=U9cwdhi+tq88ysrhVspEdoeZig3JFYbGxNh6TG9NNQ4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y/fv2OlZ5uC7nyP7zuX1T1TF4lr98o1yxLOKOzy2 s/cPPVgRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzERoRhfsX9LXpy0xgu7VRd fqla97CLd+/kLIZ52nGNK/wOGyhzqjxcN7OuslVnRlQvAA== 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: call disable_usb9pfs() from usb9pfs_disable() usb9pfs_disable() is the usb_function ->disable callback, invoked by the composite gadget core whenever the host resets or unconfigures the gadget. The gadget function API requires this callback to disable its endpoints; every other in-tree function driver does so from its ->disable hook. usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT endpoints and their usb_request objects were left active and allocated across a host-driven disable. When the host later reconfigures the device, enable_usb9pfs() calls alloc_requests() again and unconditionally overwrites usb9pfs->in_req/out_req, permanently leaking the previous allocations, while the endpoints themselves are left enabled underneath the function's own idea of being disabled. Call disable_usb9pfs() before reinit_completion(&usb9pfs->send), mirroring the same sequence already used in p9_usbg_close(). Placing it before the reinit_completion() also ensures usb_ep_disable() has synchronously flushed any requests still queued in hardware before the completion is reset, closing the same race that motivated resetting the completion here in the first place. The Linux kernel CVE team has assigned CVE-2026-99779 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.12.118 with commit 2d2e942cd9a8fc1f11e3e8e0340a0bb4ec1e9b9c Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.18.64 with commit 52544826f345280beb13d150c3bc41e61353fa0c Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.3.5 with commit 277167375d269e411e2c5ce79527ff3ebf57a0bc Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.4-rc2 with commit cd1988cf723c2eae87112b198bf90b0aebfeaf31 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-99779 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/2d2e942cd9a8fc1f11e3e8e0340a0bb4ec1e9b9c https://git.kernel.org/stable/c/52544826f345280beb13d150c3bc41e61353fa0c https://git.kernel.org/stable/c/277167375d269e411e2c5ce79527ff3ebf57a0bc https://git.kernel.org/stable/c/cd1988cf723c2eae87112b198bf90b0aebfeaf31