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 8E3593A785C for ; Sun, 19 Jul 2026 15:43:18 +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=1784475799; cv=none; b=C8PFEwzM1VqHugM9Idj+e/bE651SfVHQq+qDyEKLpJCiXLJ3cPbD/5zQZXOQd/o4IrAoB1SttYT4pdwtvMnYvuI5K2iGBNyD/HMn0mhoOgvmvPRk8zr8I5vw4NaQaBVdcIPldN0QTGX9fBK7NKacF+Kh/jWgp6is9+vOL5w3XI0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475799; c=relaxed/simple; bh=QarlUP3N9urpmIsx8+iokD/HdvUrjn/jR8SsgG+WPVs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=M0DKux3aDNzhC/FEsu0wmvV6Xl1UrpU1PPeTZnm0AY3TDQN31TJ5SXlNMfehRKwnKja7TtdM+ChhSK68Quf50GhC0yTFZIAMNWKZ+TyVXsNquBBQKIP+nJYErsN6LOjyWt2r9YGnyi8goeGBvFG6TmflmCQwpsnaj8JcalEVr/s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=2oRLHs0w; 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="2oRLHs0w" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DC5AE1F000E9; Sun, 19 Jul 2026 15:43:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784475798; bh=j9ENWT1bO+DAG3JPBD7JZKiloJAAmt4u4EjEXHQdR9s=; h=From:To:Cc:Subject:Date:Reply-To; b=2oRLHs0wBHnqoL5wdxT1aoODZTlz1CWSn9tDEQx+161+AkVRFUd7/ZRD8ij0c5Fge QnT6Ku2U1tkaHLJqYTiuyTwnN9GmnyDoybXNIPLe1V5ns0tFxKQtpK7fUWcRVWVCaz ElFTdt+IF14iYPGzI8Mx8z7eRhcT+JP3j4avY5u8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64052: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() Date: Sun, 19 Jul 2026 17:38:34 +0200 Message-ID: <2026071908-CVE-2026-64052-452e@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=3144; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=gmSKGAuP8B4/AYqhqykvIhpaMO4Gbz8+A+uJfSfvGF0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx7xMiF06p2PTjlrHllVszeVbs/SvgbxXCejak+LlxS vzKBjaGjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiIwA6G2WzPOUO+mZUnBKqn ubVp/vq9/MaSOIYF+2Y/smE53pP0fnfZpGuv8mftn3i8AgA= 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: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() pin_user_pages_fast() can partially succeed and return the number of pages that were actually pinned. However, the bio_integrity_map_user() does not handle this partial pinning. This leads to a general protection fault since bvec_from_pages() dereferences an unpinned page address, which is 0. To fix this, add a check to verify that all requested memory is pinned. If partial pinning occurs, unpin the memory and return -EFAULT. Kernel Oops: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 0 UID: 0 PID: 1061 Comm: nvme-passthroug Not tainted 7.0.0-11783-g90957f9314e8-dirty #16 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 RIP: 0010:bio_integrity_map_user.cold+0x1b0/0x9d6 The Linux kernel CVE team has assigned CVE-2026-64052 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 6.12.92 with commit 77c059f41e9395793917d067476f549a911d77d3 Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 6.18.34 with commit 76410790f1491c8e06a451045ae223a61c652455 Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 7.0.11 with commit 8fa244738641d95ea4d70e6f9a62778bba42a5b7 Issue introduced in 6.8 with commit 492c5d455969fc2e829f26ed4c83487b068f0dd7 and fixed in 7.1 with commit 8582792cf23b3d94674d4d838f7cde9a28d0fcaf 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-64052 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: block/bio-integrity.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/77c059f41e9395793917d067476f549a911d77d3 https://git.kernel.org/stable/c/76410790f1491c8e06a451045ae223a61c652455 https://git.kernel.org/stable/c/8fa244738641d95ea4d70e6f9a62778bba42a5b7 https://git.kernel.org/stable/c/8582792cf23b3d94674d4d838f7cde9a28d0fcaf