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 CAB1A443AA0 for ; Fri, 24 Jul 2026 15:30:05 +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=1784907007; cv=none; b=S1iZGZxGLY46gE1dZF7USujEavWcOeX9trHE15uOoHJ2CgwvFRwgEEAvbRHBd+J2IIUhV0miFlQE+xQhTIsgUowWYU6RGndaQ25BZCKP3sV8L2NBADldUV5xzVYYFWAIVnFNgZPqtQN3SsaGSC/aMqbstCEpl8YDMqDBziwLaIc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784907007; c=relaxed/simple; bh=RmDyvE5fVbsU4EXZdJ29aqU0g18pkRTQejikv2jQ4JI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=tpNSu0L+/npU7WG6af6B7moko2higZMk8nCht7H7MLZunPzIMNIrH88tJeX48SO0L7ztaXYYktea9q0wuDX1JIcu3mTDtbVJOr5l0lFzqROd4KNbfjs3J8YHAnet8bACqFX3OZXztaQigrDxqxWCbdjYn8dOb/ec1JlkWaP1gW0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=D7Pwdj7k; 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="D7Pwdj7k" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E82831F00A3D; Fri, 24 Jul 2026 15:30:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784907005; bh=gk1prD3x0IiP/Vzvu0VuN5uKujaFrU0xNp1OsUCcBoo=; h=From:To:Cc:Subject:Date:Reply-To; b=D7Pwdj7knsLY2zUs9+cxErNRgT8cpDhVs02mYhNWHY+Z5uO6WBOo5sEXg+ux5zdxo wrZG2ZE3DuL9rsPBVotL+Xzx5Z7v9SfIHDjSuD1avp9lc/bjP07GTdmvamVwULebvN TAJG37W72IrwuIn5+VjMF4fm/B/VjWw9/QdjinRU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64244: drivers/base/memory: set mem->altmap after successful device registration Date: Fri, 24 Jul 2026 17:29:54 +0200 Message-ID: <2026072453-CVE-2026-64244-2efd@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=3067; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6i3rQY4XH8ezqkrk8lGaGfyWRPk4yZPP05eLQV3tsZ8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFnJLR/ThKcbzO5Vl6maLa8mcuHz9bu2J7ZEdrB0ivq77 G3pW3S7I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACby+yrDPP15O55b9bKcshV1 5Di1rPr/s8P79RlmMU/4X8D0gM0u59K9NYGzZ3/akp4aBAA= 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: drivers/base/memory: set mem->altmap after successful device registration If __add_memory_block() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memory_block_release() with mem->altmap still set, causing a WARN_ON(mem->altmap). This was triggered by modifying virtio-mem driver. Fix this by delaying the assignment of mem->altmap until after __add_memory_block() has succeeded. The Linux kernel CVE team has assigned CVE-2026-64244 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit 1a8c64e110435e44e71bcd50a75663174b575f22 and fixed in 6.6.144 with commit 802e113cf120df7208e4c7e604950a85e87120a8 Issue introduced in 6.6 with commit 1a8c64e110435e44e71bcd50a75663174b575f22 and fixed in 6.12.95 with commit 22dc0d042f02ce82aa61422ea5f232628bfd9e9c Issue introduced in 6.6 with commit 1a8c64e110435e44e71bcd50a75663174b575f22 and fixed in 6.18.37 with commit 6c25bf4e44a2b6a14332f952bba0974521f5b72d Issue introduced in 6.6 with commit 1a8c64e110435e44e71bcd50a75663174b575f22 and fixed in 7.0.14 with commit bc3dd82a0ffd488bb902f4c69c3d28fd4088d973 Issue introduced in 6.6 with commit 1a8c64e110435e44e71bcd50a75663174b575f22 and fixed in 7.1.2 with commit 059ac6252a63edf1cea79bf30bd860a8c264b62c Issue introduced in 6.6 with commit 1a8c64e110435e44e71bcd50a75663174b575f22 and fixed in 7.2-rc1 with commit a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a 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-64244 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/base/memory.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/802e113cf120df7208e4c7e604950a85e87120a8 https://git.kernel.org/stable/c/22dc0d042f02ce82aa61422ea5f232628bfd9e9c https://git.kernel.org/stable/c/6c25bf4e44a2b6a14332f952bba0974521f5b72d https://git.kernel.org/stable/c/bc3dd82a0ffd488bb902f4c69c3d28fd4088d973 https://git.kernel.org/stable/c/059ac6252a63edf1cea79bf30bd860a8c264b62c https://git.kernel.org/stable/c/a2b8d7827f48ee54a686cb80e4a1d0ff954ec42a