CVE-2026-74712
vdpa/mlx5: Fix buffer length in create_direct_keys()
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.
INFO
Published Date :
Aug. 22, 2026, 4:16 p.m.
Last Modified :
Oct. 14, 2026, 1:10 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | CRITICAL | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Apply the patch to correct buffer size calculation.
- Update the Linux kernel to the fixed version.
- Rebuild and deploy the kernel.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74712.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74712 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74712
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74712 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74712 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 14, 2026
Action Type Old Value New Value Added Translation Title: Linux, Description: En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: vdpa/mlx5: Corrección de la longitud del búfer en create_direct_keys() Hemos visto en nuestro CI el siguiente mensaje de KASAN: BUG: KASAN: slab-out-of-bounds en cmd_exec+0x550/0xca0 [mlx5_core] Lectura de tamaño 272 en la dirección 0000000176795020 por la tarea 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] [...] La dirección errónea se encuentra 4128 bytes dentro de la región asignada de 4384 bytes [0000000176794000, 0000000176795120) Así que, en esencia, leemos 16 bytes más allá de la asignación de 4384 bytes. create_direct_keys calcula el puntero y la longitud para los búferes de entrada y salida. El cálculo del tamaño para la entrada incluye el tamaño de toda la estructura (salida + entrada + mtt[]) pero el puntero pasado a cmd_exec apunta solo al campo 'in', omitiendo el campo 'out'. Esto hace que mlx5_copy_to_msg() lea más allá del búfer asignado por sizeof(out) bytes al copiar datos de comando. Calcular correctamente el tamaño de entrada para que coincida con el puntero y el tamaño de asignación. -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 25, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 22, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '0071b138d44af4296bf871e6624369ce697b4b15', 'lessThan': 'ec3bb289cf19d526224117d5d450a5fd9cbd5ab2', 'versionType': 'git'}, {'status': 'affected', 'version': '0071b138d44af4296bf871e6624369ce697b4b15', 'lessThan': 'cde8931a25392670dd59a0acfcab87a830ab66c5', 'versionType': 'git'}, {'status': 'affected', 'version': '0071b138d44af4296bf871e6624369ce697b4b15', 'lessThan': '6c8a9f7bc00301e533a5366384f3070a8e7f8430', 'versionType': 'git'}, {'status': 'affected', 'version': '0071b138d44af4296bf871e6624369ce697b4b15', 'lessThan': '727e1f569855df83579edbd73dcb4a0723543a12', 'versionType': 'git'}], 'programFiles': ['drivers/vdpa/mlx5/core/mr.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.12', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.12.104', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.45', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.9', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/vdpa/mlx5/core/mr.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/6c8a9f7bc00301e533a5366384f3070a8e7f8430 Added Reference https://git.kernel.org/stable/c/727e1f569855df83579edbd73dcb4a0723543a12 Added Reference https://git.kernel.org/stable/c/cde8931a25392670dd59a0acfcab87a830ab66c5 Added Reference https://git.kernel.org/stable/c/ec3bb289cf19d526224117d5d450a5fd9cbd5ab2