From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 E660D3E277B for ; Fri, 8 May 2026 13:14:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778246067; cv=none; b=DUmKZbHaYNifcoSDs22iDE5iRNA48gEl6FFA0qEsDkVaOwp4OdUbfXMuI72v4Ihqm+BF/4mgq23XgMw1WeyxqNE3rRV2MNtKd+5fOAQ2OW80Q5ecQic7wmqQ8RkIz7RQB24cdBAJGx9Tm4JZuDRhFkCWFq2u0/pCq8TgWJww5xk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778246067; c=relaxed/simple; bh=vmWfi0hNS4ka5TXNTFtz7me4aVL0ea9FVmb3vlvnxy4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=OrPYjvGAvf7sHnvAK+ERTNhMWOquBC4OVSP1nzYfcgEznS6eIneGc2Wy6zfBDUKNZmqqz8t0IHY1gkJ+ApfirZl/zX6NJcg0M4CTUbybt0gqhqGjchoP7uCU/z+Eu5xCOAqBCNpXslG2PO8FsCDOE9gGT56dRO6rPgSeN/8pdSk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=NcgYXf+4; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="NcgYXf+4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 462C4C2BCB0; Fri, 8 May 2026 13:14:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778246066; bh=vmWfi0hNS4ka5TXNTFtz7me4aVL0ea9FVmb3vlvnxy4=; h=From:To:Cc:Subject:Date:Reply-To:From; b=NcgYXf+4MRkMwVhwJeRoEm6TLMePOWqQ7zriMKeDcL9jYO1Q0g2fho2l3WNufaOlT i96dBOdQ/3ZS++ASsWtUzgeyPvEKAgzuz2IvVHUmyN0KmaQkTAlhKCSebg2YNCN7pq gh5j9HCaop66e3aKgP3npZRZDELTFNPT4MwOCotU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43302: drm/v3d: Set DMA segment size to avoid debug warnings Date: Fri, 8 May 2026 15:12:07 +0200 Message-ID: <2026050856-CVE-2026-43302-a1f7@gregkh> X-Mailer: git-send-email 2.54.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=4096; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=mJXUry/3eeoYZTcNqASq/heyH1kR2g0xrcDhpYKqS8k=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/H8o+L2g6zVnis8pLoj58hX/EZ8ZQbmeeWRfZisq3T br79X9HRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzkSwHD/PTcc4scGM+Z1H0Q PpEuL9nS0S7ryLBg175p0Wy+e7j+Lm3i8nKoenfraEoWAA== 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: drm/v3d: Set DMA segment size to avoid debug warnings When using V3D rendering with CONFIG_DMA_API_DEBUG enabled, the kernel occasionally reports a segment size mismatch. This is because 'max_seg_size' is not set. The kernel defaults to 64K. setting 'max_seg_size' to the maximum will prevent 'debug_dma_map_sg()' from complaining about the over-mapping of the V3D segment length. DMA-API: v3d 1002000000.v3d: mapping sg segment longer than device claims to support [len=8290304] [max=65536] WARNING: CPU: 0 PID: 493 at kernel/dma/debug.c:1179 debug_dma_map_sg+0x330/0x388 CPU: 0 UID: 0 PID: 493 Comm: Xorg Not tainted 6.12.53-yocto-standard #1 Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT) pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : debug_dma_map_sg+0x330/0x388 lr : debug_dma_map_sg+0x330/0x388 sp : ffff8000829a3ac0 x29: ffff8000829a3ac0 x28: 0000000000000001 x27: ffff8000813fe000 x26: ffffc1ffc0000000 x25: ffff00010fdeb760 x24: 0000000000000000 x23: ffff8000816a9bf0 x22: 0000000000000001 x21: 0000000000000002 x20: 0000000000000002 x19: ffff00010185e810 x18: ffffffffffffffff x17: 69766564206e6168 x16: 74207265676e6f6c x15: 20746e656d676573 x14: 20677320676e6970 x13: 5d34303334393134 x12: 0000000000000000 x11: 00000000000000c0 x10: 00000000000009c0 x9 : ffff8000800e0b7c x8 : ffff00010a315ca0 x7 : ffff8000816a5110 x6 : 0000000000000001 x5 : 000000000000002b x4 : 0000000000000002 x3 : 0000000000000008 x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00010a315280 Call trace: debug_dma_map_sg+0x330/0x388 __dma_map_sg_attrs+0xc0/0x278 dma_map_sgtable+0x30/0x58 drm_gem_shmem_get_pages_sgt+0xb4/0x140 v3d_bo_create_finish+0x28/0x130 [v3d] v3d_create_bo_ioctl+0x54/0x180 [v3d] drm_ioctl_kernel+0xc8/0x140 drm_ioctl+0x2d4/0x4d8 The Linux kernel CVE team has assigned CVE-2026-43302 to this issue. Affected and fixed versions =========================== Fixed in 5.15.202 with commit 14d0d6c8b4504a60cfeea74775ab2e0164019e65 Fixed in 6.1.165 with commit 225023e3619b81af6d8d0e680503fc2d68633023 Fixed in 6.6.128 with commit 2663ef70c6123b2232190f917275e5c3175f97d0 Fixed in 6.12.75 with commit cf510785f74e74c54de40a43a955b7f844857487 Fixed in 6.18.16 with commit 0290934d30abe7c88e18140fd5184c3f386b1e44 Fixed in 6.19.6 with commit db15f469a88d3bbeeaa9f8c9f5e74d856ba5d7d2 Fixed in 7.0 with commit 9eb018828b1b30dfba689c060735c50fc5b9f704 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-43302 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/gpu/drm/v3d/v3d_drv.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/14d0d6c8b4504a60cfeea74775ab2e0164019e65 https://git.kernel.org/stable/c/225023e3619b81af6d8d0e680503fc2d68633023 https://git.kernel.org/stable/c/2663ef70c6123b2232190f917275e5c3175f97d0 https://git.kernel.org/stable/c/cf510785f74e74c54de40a43a955b7f844857487 https://git.kernel.org/stable/c/0290934d30abe7c88e18140fd5184c3f386b1e44 https://git.kernel.org/stable/c/db15f469a88d3bbeeaa9f8c9f5e74d856ba5d7d2 https://git.kernel.org/stable/c/9eb018828b1b30dfba689c060735c50fc5b9f704