CVE-2026-74712
mlx5 vDPA OOB read allows kernel/host memory leak and DoS
Is CVE-2026-74712 being exploited?
Not confirmed. CVE-2026-74712 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-74712?
CVE-2026-74712 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74712?
Yes. A fix has been recorded for CVE-2026-74712. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74712 affect?
CVE-2026-74712 affects Linux kernel (mlx5_core, mlx5_vdpa), Mellanox/NVIDIA ConnectX mlx5 NICs, vDPA-enabled virtualization (QEMU/KVM), Servers using mlx5 driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74712?
Apply Linux kernel update with mlx5_vdpa fix and reboot affected hosts; prioritize vDPA/QEMU hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds read in mlx5_vdpa create_direct_keys can leak kernel/host memory and crash kernel/QEMU, enabling info disclosure or DoS via local/guest commands.
Patch when possible
- affected>= 0071b138d44af4296bf871e6624369ce697b4b15 and < ec3bb289cf19d526224117d5d450a5fd9cbd5ab2
- affected>= 0071b138d44af4296bf871e6624369ce697b4b15 and < cde8931a25392670dd59a0acfcab87a830ab66c5
- affected>= 0071b138d44af4296bf871e6624369ce697b4b15 and < 6c8a9f7bc00301e533a5366384f3070a8e7f8430
- affected>= 0071b138d44af4296bf871e6624369ce697b4b15 and < 727e1f569855df83579edbd73dcb4a0723543a12
- affected6.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.