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=1795100069; b=EVjhSBLOpWqZnXHnjrQ0Rfb6ZKvf5rrMVCWCgHqu/9NxQSEgiN3Rb1H1R4O+79ul50BU NM3YsOOtEvJPPe6dCSOQD+rYq2t/TM9x//mN5sifpjd0VQQ6ftkFFMd49rOUH4sAazUYg SWdF41ptWoEzugEFU09ZfKH/KkatRDB+eoTS6Z/0PGDFx8zhvNZVtQTS9/fPyE7I2DiJP yGvH2PzF+NH6e25o8kuqlOsVOB6vZpTBTXTwF6y9EIlGttHuALJb0lpU5+oUcNjRk7NJE h1fJKk2S9yT/dp8EaC7TQXcQqvgWwQ9oUhxsnCvUVUvnChhNuA6XOyte0hjNugUNfRw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795100069; 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=dlu9xdG+d+nIB0f6mDDeoU/khaMGpIQPffIVWclz6KE=; b=fzhuxA6gWAlVp2MO2XWC9zY//PfmXeVy/mKP7cyNoT5ziePWoCaqY/SiG3omFAlc3Jo/ 0BGmIBufvyNqRvFns3ciV3TaX4TxX8shvhC087TX0rqQn6BaivLi9O+PFgvBo8q6qVLm1 fQ8HRIFIazTgCV2vLuv2ns1JrrS7g/gg5fWFRiFCjBk8W0+WVpAV6IMgjcFzNsinVqVbj 8S/ElSz9iA+OcUZF2kxpT+Mtg+dAqmx/WXt6ZqICIJrdPI6WVmKcyzZPvLVFRg7dYNisA CfDl6aOiifaqmmRJnPPZdDxioDbwPwEd5nEPVEJWbl9zNN38t8Fd+/PGOX/z9WC1cIg== 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=zVb2dij7; 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 16A50606A320 for ; Thu, 19 Nov 2026 14:54:28 +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=zVb2dij7 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3EA561F000C4; Thu, 19 Nov 2026 14:54:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795100068; bh=dlu9xdG+d+nIB0f6mDDeoU/khaMGpIQPffIVWclz6KE=; h=From:To:Cc:Subject:Date:Reply-To; b=zVb2dij7kjdmZBxkSpLUq/lc0MhXF+AVIqX8H3L7BLxpQO07zeXwyu/DvWw3XYHgw 2kmvLjKDtyWgMvwlTYsypAkFrxNZmIxM0lPjbhLIBX8HZ+RO3GHG6/Ncc7kAjZhcv9 aDR4ebztoVotcD57unvY2Zg695CHkkMO7ypFbgZI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99473: KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot Date: Thu, 19 Nov 2026 15:26:11 +0100 Message-ID: <2026111911-CVE-2026-99473-e2da@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=3228; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=deGV7F/iyAbE6jwxSr9rbAdG1IcWh7tWEoLwvYidiPo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2bpf8X+XLrbnL/5b9HOupNu8hVMW+Uz3cm/eZPzdr aNW9O/RjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjIPXWGBTc0v2U8Ynzyimu5 erE0S0RtzebDEQwLWl2tD11LvHhUK/3gXc9ldRNClFVnAAA= 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: KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot If inserting a memslot into a guest_memfd's bindings xarray fails, propagate the error back to the caller, i.e. fail memslot creation as well. Signalling success and continuing on with memslot creation results in use-after-free, as the guest_memfd instance will remain reachable via the memslot after the file is freed (kvm_gmem_release() won't nullify the file pointer due to lack of a valid binding). Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY is already set, partly to guard against goofs elsewhere, but mostly so that KVM doesn't need to worry about clobbering flags when unwinding on failure. Regarding the unwind, the slot must be fully prepared before inserting it into the bindings, at which point the slot becomes reachable. I.e. waiting to update the slot in order to avoid the ugly unwind isn't an option. And as part of the unwind, explicitly nullify the relevant bindings, as xarray can store a subset of entries when populating a range. The Linux kernel CVE team has assigned CVE-2026-99473 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit a7800aa80ea4d5356b8474c2302812e9d4926fa6 and fixed in 6.12.117 with commit 2cfc1ccf67ffe96811c816d27d44128c5d5833ec Issue introduced in 6.8 with commit a7800aa80ea4d5356b8474c2302812e9d4926fa6 and fixed in 6.18.63 with commit 1706461eb1af814366b6d0ab413edd0876bd8033 Issue introduced in 6.8 with commit a7800aa80ea4d5356b8474c2302812e9d4926fa6 and fixed in 7.3.2 with commit 2fa83c615f8dbb240b262265e788b120b6384e7b Issue introduced in 6.8 with commit a7800aa80ea4d5356b8474c2302812e9d4926fa6 and fixed in 7.4-rc1 with commit e6ecb88711d93b9e014532f17d3d29b57e80932c 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-99473 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: virt/kvm/guest_memfd.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/2cfc1ccf67ffe96811c816d27d44128c5d5833ec https://git.kernel.org/stable/c/1706461eb1af814366b6d0ab413edd0876bd8033 https://git.kernel.org/stable/c/2fa83c615f8dbb240b262265e788b120b6384e7b https://git.kernel.org/stable/c/e6ecb88711d93b9e014532f17d3d29b57e80932c