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=1795154537; b=AsdC0Dk8dsFnCsA8D01IeQtcsc8YcPMedonasagdeEWd/aSv9dmAyjCTSC4GcH49pA0g xUceyR+YGpjO+vwo6O9cQhFwAMaFxcmnE58DiL0+IS+Ba45YUwizN8j6/xEfNexdqwRjd gqsQTnqCU0wYNpVaA8/iwHM+taVoFT1UN/Sh+dfa12sm6pnRT6rHwSk4dfwsZ1u2697C7 rGlKbXHUOqxfOLvf+cbKygWYPX1pB9+3tkfIL50FUMGFHnGDrDq47GYkV9Yav6r96my+c +IfSWrjVI22OkylGlHrLVuOniRPybNbN4lOd/19bTTO5KshUCsq9njLV60+Q9/pCgFg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154537; 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=xQmaJiQkDVEnwOSRAwmwPfZ3vSk7HZNcNLQjW5Jn5go=; b=V3ApziOr0QmtHP4yzMPzCDnmgELUzVhQZYPJ+2JtmIRGOjVCkinnaMGOAbzJ69+mnT4d i21LtOLQ4fxEV8WDxD6A8Pjz0LiE8kwVxlBx8WdBhgPXoJEp7HP4pNYvWORlZiAVJiseA 7EAjrsWUt0srexKcPVAe2NkJV+jwHzkfi5dNChVlmFcaczC4P9j2ldFS7aWiXdYeWn6mA YokI0KCCdkgaEG2NG8NJ5Vd2JoFMnm0eSV6FLaltbSyxuJB+yEwTlt3kcRscK1pzMVnPl ovEoiamRhHWS69K+WtQqc1tSBF0XtT7BZa9PyQKqsg75L+ljYBEoeW+4jnoH4okvXlQ== 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=DDTSHd4I; 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 8ED32606A334 for ; Fri, 20 Nov 2026 06:02:17 +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=DDTSHd4I Received: by smtp.kernel.org (Postfix) with ESMTPSA id DE8201F000C6; Fri, 20 Nov 2026 06:02:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154537; bh=xQmaJiQkDVEnwOSRAwmwPfZ3vSk7HZNcNLQjW5Jn5go=; h=From:To:Cc:Subject:Date:Reply-To; b=DDTSHd4IcsPSDuN0ogtmDDZUxsKI2ce0G7ZMitx+iGLY9kUXM4jPnXPyHjak9AwT4 ETDREkvqxAlzHw/oX+V2Ol7wyUiK7Xu+BV2SYyh3vfSF4GJibj3KwBk/9KDIM/9zs/ J88m3UkPZ1BZlQId8cx/j/CDGYlIBZpqUxH/jsCM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99778: net/9p/usbg: fix out_req buffer leak in disable_usb9pfs Date: Fri, 20 Nov 2026 06:52:44 +0100 Message-ID: <2026112031-CVE-2026-99778-fb82@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=2642; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=teRUvKQz2Y8fOmgnjFsIDnicdoyddqXARYQnWiNbPNU=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y//o2CdrHxc3vranMm/V+hbXG0sPZhaGjclO2nuw nDvu2wTO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiRRkMc0WKkjenKVycmrHB y+vkhU2bTA6Jb2OYn1sf9jJrzcGoqcaqC+3XhXp1XuAJAQA= 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: fix out_req buffer leak in disable_usb9pfs usb9pfs->out_req is allocated with alloc_ep_req(), which also allocates the request's data buffer (req->buf). disable_usb9pfs() frees it with plain usb_ep_free_request(), which only frees the usb_request structure itself and leaks req->buf on every close. Use free_ep_req() instead, matching the allocator, as documented by its own comment ("Requests allocated via alloc_ep_req() *must* be freed by free_ep_req()"). The Linux kernel CVE team has assigned CVE-2026-99778 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.12.118 with commit b941883db4f3ea5bf57bc8600f945f07b8ba2115 Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.18.64 with commit fbdc36c04927c08eb676a5db2120e986654ad17c Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.3.5 with commit 9ea2ffacee886707b8728c6b62d9e9650e2733ec Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 7.4-rc2 with commit 5f9807270c7bda8f86b312ed1a8acd7716600555 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-99778 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/b941883db4f3ea5bf57bc8600f945f07b8ba2115 https://git.kernel.org/stable/c/fbdc36c04927c08eb676a5db2120e986654ad17c https://git.kernel.org/stable/c/9ea2ffacee886707b8728c6b62d9e9650e2733ec https://git.kernel.org/stable/c/5f9807270c7bda8f86b312ed1a8acd7716600555