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=1795154199; b=kqIr9089xjXElkwc1F9uMELklx/EJTE6vikplX3jHwOo80eEF6qzzVkffnMCMMswXJX0 w1IdIsB3c0lRiNyi88BG57F5mO4kzpusClysVZ6ktj+RwImVTt472kdiANgjJyuADBvo2 9001yOeJuD/skmkfxSJkov4Zk4GsShaCf2WGwOhnGXG94Xt41vDNRJ1tgEL8g5RSMNMDc DVDDWW55Ps+jNMfcD7YRIOPbCFFFTdwe8IkplJdl3+MNZBm6vHD9p+2RJmGKOuL2YQJAK hFVkETSedz3UT37DJ+Syxw6mBYFq3QkIpVeKD4Vr3Nxc0hmd1FtrVFs0NJMPlplDWyw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154199; 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=XnnSakLTbUJPXPbdN/N6UZiNwiUCZzTUUH9rK1C3rwI=; b=lYcF8X0lmvMpI4E+DFW1DGc9qsUKNGhkTixhPVg0eaFaQb7kvyU9ABnIidK7vdHCTUWP yW8MjZjzQGmr7+Tk2eHu2ESsujpRt5wbpuRl3l7XrQrO2NQg2aHBVZx/iyJIErI/mJhS0 BPh5m8DWxA+eSWuFRvPhhhzvQHYMsNbimqXIJD/7QyZUEeCuioOl9lYaaB9QBNpea81w3 1/jOdNMm/RS/nBxSKUrGLQ+d9XzPZOgfOnEBzttwjvxCLe7cdpdz6CE/smRLwsDwWXis+ NDkx4cgjX613bTMoMQv1NMSsA7ygKazK3yphsbjMJZbmACwxToooENh75sEKQImsPYQ== 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=Uv2jLBV2; 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 1BAA9606A320 for ; Fri, 20 Nov 2026 05:56:39 +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=Uv2jLBV2 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6AF2B1F000C4; Fri, 20 Nov 2026 05:56:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154199; bh=XnnSakLTbUJPXPbdN/N6UZiNwiUCZzTUUH9rK1C3rwI=; h=From:To:Cc:Subject:Date:Reply-To; b=Uv2jLBV2/SuLf52EsOeKPd6ut+Z+nf1fNCs9uWWGY4PjQ64erfOp4r1PJf6+7jqwT IGCiQwwFT6uYC/uAwqAiQ8lWFUs7W9j/xsb9RCO7euKBx3RsCxFQ5y1lBAJLhD2Ety WRDQKJc/2PMuoQSNuwohKGkUIipBen560sVfQ298= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99660: mm/userfaultfd: write-lock the VMA before waking waiters when unregistering Date: Fri, 20 Nov 2026 06:50:46 +0100 Message-ID: <2026112047-CVE-2026-99660-fbba@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=2289; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=gFfWd1cHhkJIIQVLmCM+NFWgpzvOlN/VqHH5kzFuKaY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/71c/271lR/vliZqVuoovrN9EXLq94d6HXK0dtywO9 Fmyr0j+0xHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATYatkWNDf6zi/ccu9ik96 +tEuv9uPfI+f9IJhwfYje8OWPinh/vlp2nNnwRJm3ZCddwE= 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: mm/userfaultfd: write-lock the VMA before waking waiters when unregistering userfaultfd_unregister() wakes pending missing faults before clearing the VMA's userfaultfd registration. With per-VMA fault locking, holding mmap_lock for write does not prevent another fault from queuing after the wakeup but before userfaultfd_clear_vma() write-locks the VMA. That waiter can then remain asleep indefinitely. Call vma_start_write() before waking waiters. Existing fault handlers queue themselves before dropping the VMA read lock, and new readers are excluded until mmap_write_unlock(). The Linux kernel CVE team has assigned CVE-2026-99660 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit 29a22b9e08d70d6c9b075c12c47b6e895cb65cf0 and fixed in 7.3.5 with commit 8a47f699a5c184071bb1dc52f08f98c85bfb85a3 Issue introduced in 6.6 with commit 29a22b9e08d70d6c9b075c12c47b6e895cb65cf0 and fixed in 7.4-rc2 with commit 35f7ecd55ce7e51cb6d5ef49e6dd51f3c80f61e4 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-99660 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: mm/userfaultfd.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/8a47f699a5c184071bb1dc52f08f98c85bfb85a3 https://git.kernel.org/stable/c/35f7ecd55ce7e51cb6d5ef49e6dd51f3c80f61e4