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=1795154176; b=tu5L+y8iHgtv3m8VQHjOpDyvF5E2bJEb1X5ywL2WcSPYlpe3swQqVsMDSxRb7Mpb70qP p/Om7henGIIK8at/unEy25sc5I63ldIqlRp7/9a3JQAYdLApVG63Yd/b9ft0TjE9EAgas HRl36GhL7dMHR/1pInGFa6k9IgWpxQE6qk9eifLikG/4b0drWXWPsZ/PMcrugjpMplf0X Epfz5dgfiWD18Rx92ZPaouWtSOTkYdENRnZjzYmo0Duj0lEGmUGIOYHgeBI7NIa1DgX6R qaf1PtK7G/VQ/SNQaqiIVECcNIXbLqqHxOCHvCx/dN/0TB5DpIe2Seg3J/pOaTj6q5g== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154176; 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=YIZgjEv3dgRifmAwUOgBf6+VfwPIwxcVqq7vUgWzDOc=; b=MX9NRU4kb4MqJ9YlFxu3VgqQzCHaZ5YdBbBVsH6AyuJ9vTDeNg2Om21Gbp/VtkAr5QhC 4I3oYyQBdeXjPXh7Nu/vMAN+yI2GcJAvVJLc9M8saX97+uDppB9EvrIxKWCPCE0RYaMcm uQuS4VWbkgiKEaWu5f3vw00QazWXwkRT/LiQcZJSyh2dVj8IuPODzAi1/bXsk+gYe1JHp 54m8aLZvDhLXkAQKojOIdeaGZwuw0bc+NgPekAY64TdVOhBt10mPnk4VqJTG8tRnhIegE 73czMpg8rwlmsIiISmpHezyKKBFpzOFX1XhIVs9md41uWa4GaaAX2deIubh2JjUf+gg== 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=SjeeGGhH; 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 776C4606A320 for ; Fri, 20 Nov 2026 05:56:16 +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=SjeeGGhH Received: by smtp.kernel.org (Postfix) with ESMTPSA id C61F11F000C4; Fri, 20 Nov 2026 05:56:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154176; bh=YIZgjEv3dgRifmAwUOgBf6+VfwPIwxcVqq7vUgWzDOc=; h=From:To:Cc:Subject:Date:Reply-To; b=SjeeGGhHfOYsNaET3G17bnkYJaxWmZFxJuzbbCLROxMiV1PfhLkDqVUmKc7HI+AgX +pi38jkFaInErNe3tZ2rwOWOikARAPoc+oPgTPWQXfZyLPvhcMlWSMcLAmoH6WaMGQ Mm3jahMoHxEtLvCzYzIwuisNGVcDAXeNg+udcFtk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99635: vhost/vsock: size receive SKBs from declared payload Date: Fri, 20 Nov 2026 06:50:21 +0100 Message-ID: <2026112038-CVE-2026-99635-af4e@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=3639; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=uVCnLCxMCoxeQzBdYp+G4GFAJZVako4ThJqziXueEsc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7xel8dSHHFlntfj1k3ju37ybF3Soe9sVS7mcq3Oe8 C09NCGlI4aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACayhIVhxnrP15Nm5e6/P//l xM5vFy7s25/HxLBg/5ZpOtz/fm55t7RhGkf1rr0anzlyAQ== 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: vhost/vsock: size receive SKBs from declared payload vhost_vsock_alloc_skb() sizes the skb from iov_length(), the total guest descriptor length. virtio_transport_inc_rx_pkt() instead adds hdr->len to rx_bytes and buf_used, and budgets each queued skb as SKB_TRUESIZE(0). The guest controls the descriptor length and hdr->len independently. A guest can therefore provide a 64 KiB descriptor while declaring a zero payload. The descriptor-sized skb remains queued, rx_bytes and buf_used remain unchanged, and only the fixed queue-entry budget limits retention. This is not a lifetime leak: the skb is freed when dequeued or at socket teardown. Repeating this across connections can nevertheless exhaust host memory. On Linux v7.2, 455 such descriptors retained 30,255,680 bytes for a 262,144-byte receive buffer; a full-payload control retained 265,984 bytes. Vhost previously read hdr->len and allocated pkt->buf from that value. The conversion from virtio_vsock_pkt to sk_buff instead allocated receive skbs from the descriptor length, introducing the allocation-accounting mismatch. Copy the header into a stack object and validate hdr->len before allocating the skb. Size the allocation as sizeof(hdr) + payload_len so descriptor capacity no longer determines queued memory. Check payload_len against len - sizeof(hdr) to avoid addition overflow on 32-bit hosts. The Linux kernel CVE team has assigned CVE-2026-99635 to this issue. Affected and fixed versions =========================== Issue introduced in 6.3 with commit 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 and fixed in 6.12.118 with commit 92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8 Issue introduced in 6.3 with commit 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 and fixed in 6.18.64 with commit 89a2f2251a06751ddabbd6a39c207236b8bd42d5 Issue introduced in 6.3 with commit 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 and fixed in 7.3.5 with commit 9819add3aeb66dc823db0a82337f55481ad463be Issue introduced in 6.3 with commit 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 and fixed in 7.4-rc2 with commit d5e912448cd98b261eba8e35ab838f2dc69a79f5 Issue introduced in 6.1.63 with commit baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 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-99635 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: drivers/vhost/vsock.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/92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8 https://git.kernel.org/stable/c/89a2f2251a06751ddabbd6a39c207236b8bd42d5 https://git.kernel.org/stable/c/9819add3aeb66dc823db0a82337f55481ad463be https://git.kernel.org/stable/c/d5e912448cd98b261eba8e35ab838f2dc69a79f5