From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7C6B133EAF9 for ; Sat, 22 Aug 2026 15:34:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787412876; cv=none; b=jyHPRq+JJlbRnG/yj4vKJ99Qp9k0XfF7egULif0R69KEMsbSprIP3nTJsj71NhRs3lkHO++vBEM+CeZFUVA1mt0KwM7MGVKvS/NV6M63sg+MrFYboddanVPcsxGV+m6I0ruCQZJDOlNv3iQe2tehjOhyO7hIKcY0azS/ezUXIko= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787412876; c=relaxed/simple; bh=RJXAGe5l/uiwx388gIbbCUbxqa3ErKQ4JftxX54PT8Y=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=abekio5jdGeHz6gM2SHIGZ5Cz/Wd3ml+xO/YBCFtnZQPsa7tKiqIm+oBlcaYK4iXce0xmuApFzYutzRZ+ARQ5XurPe07M5dHjZSg60i/UycHr2HYOiJmz4/uRjzxSDdvF4jCb+DuzRWAqftStJgWzMtoQfbhaC51BKzMTe50zfU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=kaPd2Ykf; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="kaPd2Ykf" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AC8001F000E9; Sat, 22 Aug 2026 15:34:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787412875; bh=YmAliF5Rb321Dz1vd9f27yT9U83y+DOWZdnXIFscrMg=; h=From:To:Cc:Subject:Date:Reply-To; b=kaPd2YkfUvpmefUL/2SWq2Mekaej9z8HGIL3F5X+auk9pGdAPW96qwx9xELm8Ih6R nutUfgFqtGRPLap8PRYmXo9NYKeSolJ7QfmxybpKEnBvNfC5lbjR9tJf0USsikPK/H gG0xhG0vonsza19W19is1vZg/JT33UJW9NYosUiI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74613: vsock/virtio: avoid refilling the RX queue after teardown Date: Sat, 22 Aug 2026 17:31:37 +0200 Message-ID: <2026082217-CVE-2026-74613-3b63@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4601; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ERQoHC0xyf3wH0cOIx4mGEB3SL4027Kr6lAn71OKYw0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmdB45N61ctPey99oTiu7Swxw5vRbP7snZMLFyaubFms nvL1WKzjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiI3jOG+QU5MrHfur/MWDBx ocLPKAmr6qX71Bnmh7H97vFN8zCLYM7w3x7wPPP9y8y3AA== 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: vsock/virtio: avoid refilling the RX queue after teardown Commit b917507e5ad9 ("vsock/virtio: stop workers during the .remove()") made the RX worker jump to its common exit when rx_run is clear. That exit still refills the RX queue when the buffer count is low, so work queued across virtio_vsock_vqs_del() can add buffers after the virtqueues have been deleted. BUG: KASAN: slab-use-after-free in virtqueue_add_sgs Read of size 4 by task kworker/0:1 Workqueue: virtio_vsock virtio_transport_rx_work Call Trace: virtqueue_add_sgs (drivers/virtio/virtio_ring.c:2796) virtio_vsock_rx_fill (net/vmw_vsock/virtio_transport.c:332) virtio_transport_rx_work (net/vmw_vsock/virtio_transport.c:701) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) ... Freed by task 141: kfree (mm/slub.c:6566) vp_del_vq (drivers/virtio/virtio_pci_common.c:259) vp_del_vqs (drivers/virtio/virtio_pci_common.c:285) virtio_vsock_freeze (net/vmw_vsock/virtio_transport.c:912) virtio_device_freeze (drivers/virtio/virtio.c:658) virtio_pci_freeze (drivers/virtio/virtio_pci_common.c:601) pci_pm_freeze (drivers/pci/pci-driver.c:1098) device_suspend (drivers/base/power/main.c:1968) Kernel panic - not syncing: KASAN: panic_on_warn set ... Jump to a no-refill exit when rx_run is clear, leaving the normal exit to replenish a running queue. The Linux kernel CVE team has assigned CVE-2026-74613 to this issue. Affected and fixed versions =========================== Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 5.10.265 with commit a7658508f5fe8f1077a65e8cb9535d3426f37a2f Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 5.15.216 with commit 1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171 Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 6.1.183 with commit 4d37e3525cc346a1421c1bdeaad5848e249fc60c Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 6.6.152 with commit 9d80a04129a6c27a690cb69de3fe3f50be5aa8b9 Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 6.12.104 with commit a309b74e3fc052352ab778500449cb9c3853c363 Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 6.18.45 with commit 38c7763fdc533edb34dc8f4489c260e8ba2ccae9 Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 7.1.9 with commit e82a5faea2e3886dfb2a65ce092a132e7e896915 Issue introduced in 5.3 with commit b917507e5ad983085d29069369778b16aa03a0a8 and fixed in 7.2 with commit a31e0ad444698d8aa7534a0f89fda543730f97a5 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-74613 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/vmw_vsock/virtio_transport.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/a7658508f5fe8f1077a65e8cb9535d3426f37a2f https://git.kernel.org/stable/c/1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171 https://git.kernel.org/stable/c/4d37e3525cc346a1421c1bdeaad5848e249fc60c https://git.kernel.org/stable/c/9d80a04129a6c27a690cb69de3fe3f50be5aa8b9 https://git.kernel.org/stable/c/a309b74e3fc052352ab778500449cb9c3853c363 https://git.kernel.org/stable/c/38c7763fdc533edb34dc8f4489c260e8ba2ccae9 https://git.kernel.org/stable/c/e82a5faea2e3886dfb2a65ce092a132e7e896915 https://git.kernel.org/stable/c/a31e0ad444698d8aa7534a0f89fda543730f97a5