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=1795099953; b=kDcEIa4UuBi+huZmfLln5o3ZcyEZF7gnkNnTX+hko5zGwTyYTKv6I652ozO4zxXphfQu xEPbf5fGcThknHhKk7jvign+H+IIS49tPLBnY1nyqjnRXeWLPmyboFTV+jo6sgsMLfxVs 4bK00s8UohynvumwKsGd1cMNBpNj65UFKazdy3OMfkFbTckDCAh2oX4KibURn6NA+cWu4 i0UhOyB7OI1WN2U9gvSS39swkKyrHe6p5D4we8OYrwYwC1mGw+zjylHRCUCy6dyT2pJKL ELVOeG/2bHxdD0Yys2hOFak0rI6zqqDER+aj3COnMvlHzFPd3BYxVl6c4vU+XAcSeGA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099953; 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=l0KvrhGara2wdKw/e3/xCsJY0rM/TCru56eOEp5VG9k=; b=0gJue5sHGwdXxw1ZiMbDcZ3ofYofE5hhCsyX+9NtsklTW6OHc33h6IwaFgDVVfiSJhe+ h+hIaBSU43onPXbWc9sXMC0RBw7hhCIZTm8Fzk+plXGgcO9w5/9X/qCXI3EhX9gGA8iVe q82Xwz6AefQ+SHYzBX/thRXAjHGFt7hL23mQk+BA1Gnhilo4VZtMyx0m9+9kJNS0aN2BH DSg/D8ExypFJHXG8BC4XsQHjodMESTwOkQwH6anyTDJ9Lr0CujF6j0mY9+LAjqegNJqaz X/bkaEhP+Xj71lsYHOQ3E4CBDZ5Smq8sBiZzywCJb1ghqGUF/wFSt6btrF3ALM9NoXA== 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=jm7QYoSB; 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 345A2606A33F for ; Thu, 19 Nov 2026 14:52:33 +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=jm7QYoSB Received: by smtp.kernel.org (Postfix) with ESMTPSA id 85F181F000C4; Thu, 19 Nov 2026 14:52:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099953; bh=l0KvrhGara2wdKw/e3/xCsJY0rM/TCru56eOEp5VG9k=; h=From:To:Cc:Subject:Date:Reply-To; b=jm7QYoSBzvUQx/1CyIe87/RjsuX4ASZLPYMRHHDaTy+1BHARmj+7e4FbDkRQow6eD l4RzfKnSpa0Bh+xkAFpXARfTmDE5i1NzHpRTWICyR2Hmy9SMNq6jbAHD8n1/jDx835 MijqoRFf0dTxTfvVSF2+ezlFR/c/yMtWqYOvSb/E= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99459: mshv_vtl: detach poll waiter on POLLFREE Date: Thu, 19 Nov 2026 15:25:57 +0100 Message-ID: <2026111908-CVE-2026-99459-ca4c@gregkh> X-Mailer: git-send-email 2.56.0 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=3013; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=UXjhu+vqIn9tmp8EpKka8yy4FftoVqxknkTy9yBoEu4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2Tpuxv2LEdToPMkUElvvapa17eGtkxzbnvzL7J+YL TTtQ8b1jlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhILBvD/MSPm39fumrZ1Hnk yHm7vNmH9s0Mfs8wP+6fU/2F1D/Mu7tq967f/DpS4cY7WQA= 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: mshv_vtl: detach poll waiter on POLLFREE MSHV_SET_POLL_FILE keeps a poll wait entry after the ioctl returns. A file reference does not always pin the registered waitqueue: signalfd_poll() uses current->sighand->signalfd_wqh, whose lifetime is tied to the task. signalfd_cleanup() sends POLLFREE before the sighand is freed. The MSHV callback currently leaves its entry linked, so __wake_up_pollfree() warns and a later replacement calls remove_wait_queue() through a stale wqh pointer. A source-equivalent KASAN run reproduced: BUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave _raw_spin_lock_irqsave remove_wait_queue harness_ioctl [mshv_pollfree_harness] The object belonged to sighand_cache and had been released through slab_free_after_rcu_debug() after __cleanup_sighand(). On POLLFREE, unlink the entry under the provider waitqueue lock. Preserve the existing CPU cancellation before publishing a NULL wqh, since a NULL load lets a racing replacement reuse the persistent poll state. Use a matching acquire load under RCU when removing a normal registration. The callback takes no mutex and does not sleep, so the existing mutex-to-waitqueue-lock order is unchanged. An LLM assisted the source audit, fix development, and validation of this issue. The Linux kernel CVE team has assigned CVE-2026-99459 to this issue. Affected and fixed versions =========================== Issue introduced in 6.19 with commit 7bfe3b8ea6e30437e01fcb8e4f56ef6e4d986d0f and fixed in 7.3.2 with commit ce2b83e47af491f4b7f0f286367b34cdc57e17e9 Issue introduced in 6.19 with commit 7bfe3b8ea6e30437e01fcb8e4f56ef6e4d986d0f and fixed in 7.4-rc1 with commit efc5dc4c15713fdd6e87882686a26ed1deb22dab 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-99459 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/hv/mshv_vtl_main.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/ce2b83e47af491f4b7f0f286367b34cdc57e17e9 https://git.kernel.org/stable/c/efc5dc4c15713fdd6e87882686a26ed1deb22dab