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 098423AA4EA for ; Sun, 19 Jul 2026 15:47:41 +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=1784476062; cv=none; b=FvelgvsY3R9/vLOcAwCfqD9fDkf4efwK+d7Z4CQ9k1x012mOjbju1KEAy3J5aInFnGe+1id0Jie1tfVeKfvnpP8hplIAIu3HUYlB34a83QSYsAxVhx9ATxgg0+IxZVDCIzAagAoObJM9HJRE0y1mhLA05SqJik5O4zCReSUE+uo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784476062; c=relaxed/simple; bh=qi8hhHHu0U7Je75fbn/yFrQTzc6zOQUH4TUAYTVnrVI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=LU06E4MVOQgwStFmGJIM1D87zTE69YaijTCM5iWMEi1dxu1LQgSH+ZCiSnEAvumP7XPTx6puJltEWR5mlVHEA0MxbrOj5+4+jXa89q/quT3m94IGolhmeVgOeybACY4kuXUUIuTzCjNwIBPSTCOMgrJ1kSraRD7qiYfOnflgMEc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=g5B42aOc; 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="g5B42aOc" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5879B1F000E9; Sun, 19 Jul 2026 15:47:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784476060; bh=nA1ISa+ftwREVshPxHQ9viGDg1iHTwIS1PlnvtGDH2g=; h=From:To:Cc:Subject:Date:Reply-To; b=g5B42aOccrH0wqXvyIS6cIZvZ05ptYA4XjEM5Sf7e4fYSCcf/47eB2/fGBmTmEoLf gqIMunS595LXgi/zHutm+gYUs9l6ZdBLmdJvHaXD7v8hCKzDTwgSJLUu37X53+9XGo 3tR4WdA5/VBmG5k729s9IkkYmQVixFTKGHc8ObU0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64182: drivers/base/memory: fix memory block reference leak in poison accounting Date: Sun, 19 Jul 2026 17:40:44 +0200 Message-ID: <2026071938-CVE-2026-64182-c1a7@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=2804; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=JG7pYUXe9Hy6IKMKQZm/3buRTWpQvRXJzdZrYTlbOBE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx7+v4Tf0LvyvHbfsTerTE027d9SNui86zFTmc2Vzwe cU7pYLfHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARhgqGueLnefK+8kd9VfFP Ss1l4HpWo3v8DMMsZpMd1lPVDzM+3nxp0sk5zFdFtj59CAA= 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: fix memory block reference leak in poison accounting memblk_nr_poison_inc() and memblk_nr_poison_sub() look up a memory block via find_memory_block_by_id(), which acquires a reference to the memory block device. Both helpers use the returned memory block without dropping that reference, leaking the device reference on each successful lookup. Drop the reference after updating nr_hwpoison. The Linux kernel CVE team has assigned CVE-2026-64182 to this issue. Affected and fixed versions =========================== Issue introduced in 6.2 with commit 5033091de814ab4b5623faed2755f3064e19e2d2 and fixed in 6.6.142 with commit 686b4283f82cd630fafd7ca9b03dfc080b3ec8fa Issue introduced in 6.2 with commit 5033091de814ab4b5623faed2755f3064e19e2d2 and fixed in 6.12.92 with commit ce60d9452a0f2effa72fd20ea270c59ca691d455 Issue introduced in 6.2 with commit 5033091de814ab4b5623faed2755f3064e19e2d2 and fixed in 6.18.34 with commit 24840b3139d7415144b81e4f9f4c44670d15bed9 Issue introduced in 6.2 with commit 5033091de814ab4b5623faed2755f3064e19e2d2 and fixed in 7.0.11 with commit 8502e2c2d0633f99d94d22ae8dabc10caae1fc2a Issue introduced in 6.2 with commit 5033091de814ab4b5623faed2755f3064e19e2d2 and fixed in 7.1 with commit 03a2cc1756a0570f887d624cd6c535ea0cbd4951 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-64182 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/686b4283f82cd630fafd7ca9b03dfc080b3ec8fa https://git.kernel.org/stable/c/ce60d9452a0f2effa72fd20ea270c59ca691d455 https://git.kernel.org/stable/c/24840b3139d7415144b81e4f9f4c44670d15bed9 https://git.kernel.org/stable/c/8502e2c2d0633f99d94d22ae8dabc10caae1fc2a https://git.kernel.org/stable/c/03a2cc1756a0570f887d624cd6c535ea0cbd4951