From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys()
Date: Sat, 22 Aug 2026 17:33:16 +0200 [thread overview]
Message-ID: <2026082238-CVE-2026-74712-1399@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-08-22 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026082238-CVE-2026-74712-1399@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.