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 989063DAAC9 for ; Sat, 22 Aug 2026 15:39:45 +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=1787413186; cv=none; b=lZ109qHlScIcSmmwO05oPXXQKCOutm+gwwdJeeCpKZk5mj17EQNhgmIULafUR83o2um8vAT0h0Z9Di9n7iFkJHHXGq5Lya0YiF+YYYoBr4gl4Ga4DJVPol/9zbtmiV9BiQsdIYAR/1d3wv6gGWHTxuWEGARbUl9ymFzj7Dydjjw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787413186; c=relaxed/simple; bh=p7or/tiFtGeMGJfXvIYr14hisrGvEtC8SHJvVMur4mI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=uHYx2uXjjPX7leK9XeUVyZWndSTYGxwSvDHvUPp1kpQXcTy58HH6hZq9rfg61WysSIVlwJWCa40sHc0Lp1dBjkZ0E8K7Jgii+2RXlqkZ4KpLU8cU+A9Xn8//XstNcKehvkzVnn0Zg9qPllaKpyTagzvklDv2+cldRGheLoOI/aU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=08dvcizR; 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="08dvcizR" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F06761F000E9; Sat, 22 Aug 2026 15:39:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787413185; bh=e9pN4JXect7EWFliko2oygBYK9EHluZqsPl3MmEFo5E=; h=From:To:Cc:Subject:Date:Reply-To; b=08dvcizRirhHULmHgxRsR6//Qf40W/YvCxML1cW7EZHV8oKlFQlWK2M+bHYYCjzdR 4RqTNbmAsCQzumkkqv8gUZw5tjIWHv6eEotdDlA+VBs67EDN2yjJICJcStIohjneJR l8T2e6NOPHXZ8qu8XkxfnG2CKkpWaZ+CizjhxaHE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys() Date: Sat, 22 Aug 2026 17:33:16 +0200 Message-ID: <2026082238-CVE-2026-74712-1399@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=3314; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=BDsxpMTXAhPZ80+MyJjyBW76Npzq4iMnTOvNEP9oYB4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmdB27Nzft4WUx/ikv93XMXix8XnnovwpP5W7nA1YZp5 7WjrxsNOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAipw8zLDh36IjjAcHoRa8U VkVPmbek/+e7oucMMxlnurhwJDyd47j9os05zTdnPx85kwIA 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: vdpa/mlx5: Fix buffer length in create_direct_keys() We have seen in our CI the following KASAN message: BUG: KASAN: slab-out-of-bounds in cmd_exec+0x550/0xca0 [mlx5_core] Read of size 272 at addr 0000000176795020 by task qemu-system-s39/82764 [...] [<000011388ab3a7a0>] cmd_exec+0x550/0xca0 [mlx5_core] [<000011388ab3b61c>] mlx5_cmd_exec_cb+0x25c/0x4f0 [mlx5_core] [<000011388b21e82e>] mlx5_vdpa_exec_async_cmds+0x22e/0x5e0 [mlx5_vdpa] [<000011388b21fd44>] create_direct_keys+0x954/0xef0 [mlx5_vdpa] [...] The buggy address is located 4128 bytes inside of allocated 4384-byte region [0000000176794000, 0000000176795120) So in essence we read 16 bytes beyond 4384-byte allocation. create_direct_keys calculates the pointer and length for in and out buffers. The size calculation for in includes the entire structure size (out + in + mtt[]) but the pointer passed to cmd_exec points only to the 'in' field, skipping the 'out' field. This causes mlx5_copy_to_msg() to read beyond the allocated buffer by sizeof(out) bytes when copying command data. Properly calculate the input size to match the pointer and allocation size. The Linux kernel CVE team has assigned CVE-2026-74712 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit 0071b138d44af4296bf871e6624369ce697b4b15 and fixed in 6.12.104 with commit ec3bb289cf19d526224117d5d450a5fd9cbd5ab2 Issue introduced in 6.12 with commit 0071b138d44af4296bf871e6624369ce697b4b15 and fixed in 6.18.45 with commit cde8931a25392670dd59a0acfcab87a830ab66c5 Issue introduced in 6.12 with commit 0071b138d44af4296bf871e6624369ce697b4b15 and fixed in 7.1.9 with commit 6c8a9f7bc00301e533a5366384f3070a8e7f8430 Issue introduced in 6.12 with commit 0071b138d44af4296bf871e6624369ce697b4b15 and fixed in 7.2 with commit 727e1f569855df83579edbd73dcb4a0723543a12 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-74712 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/vdpa/mlx5/core/mr.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/ec3bb289cf19d526224117d5d450a5fd9cbd5ab2 https://git.kernel.org/stable/c/cde8931a25392670dd59a0acfcab87a830ab66c5 https://git.kernel.org/stable/c/6c8a9f7bc00301e533a5366384f3070a8e7f8430 https://git.kernel.org/stable/c/727e1f569855df83579edbd73dcb4a0723543a12