CVE-2026-74712vdpa/mlx5: Fix buffer length in create_direct_keys()
- 9.3CriticalCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 3 days later
· 3 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 96% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.3.
Affected products
- affected 0071b138d44af4296bf871e6624369ce697b4b15 – < ec3bb289cf19d526224117d5d450a5fd9cbd5ab2
- affected 0071b138d44af4296bf871e6624369ce697b4b15 – < cde8931a25392670dd59a0acfcab87a830ab66c5
- affected 0071b138d44af4296bf871e6624369ce697b4b15 – < 6c8a9f7bc00301e533a5366384f3070a8e7f8430
- affected 0071b138d44af4296bf871e6624369ce697b4b15 – < 727e1f569855df83579edbd73dcb4a0723543a12
- affected 6.12
- unaffected < 6.12
- unaffected 6.12.104 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/ec3bb289cf19d526224117d5d450a5fd9cbd5ab2 (opens in a new tab)
- https://git.kernel.org/stable/c/cde8931a25392670dd59a0acfcab87a830ab66c5 (opens in a new tab)
- https://git.kernel.org/stable/c/6c8a9f7bc00301e533a5366384f3070a8e7f8430 (opens in a new tab)
- https://git.kernel.org/stable/c/727e1f569855df83579edbd73dcb4a0723543a12 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-64399 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74712)Record last updated .