CVE-2026-74712
Last modified
CVE-2026-74712 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 0071b138d44af4296bf871e6624369ce697b4b15, < ec3bb289cf19d526224117d5d450a5fd9cbd5ab2; >= 0071b138d44af4296bf871e6624369ce697b4b15, < cde8931a25392670dd59a0acfcab87a830ab66c5; >= 0071b138d44af4296bf871e6624369ce697b4b15, < 6c8a9f7bc00301e533a5366384f3070a8e7f8430; >= 0071b138d44af4296bf871e6624369ce697b4b15, < 727e1f569855df83579edbd73dcb4a0723543a12 |
| Linux | Linux | 6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74712?
How severe is CVE-2026-74712?
How do I fix CVE-2026-74712?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74707In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74708In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74709In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7471GitLab has remediated an issue in GitLab EE affecting all ve…3.5
- CVE-2026-74710In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74711In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-74713In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-74714In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74715In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74716In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74717In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-74718In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74712?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
