CVE-2026-74712

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-22. a secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

vdpa/mlx5: Fix buffer length in create_direct_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec3bb289cf19d526224117d5d450a5fd9cbd5ab2
generic

vdpa/mlx5: Fix buffer length in create_direct_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cde8931a25392670dd59a0acfcab87a830ab66c5
generic

vdpa/mlx5: Fix buffer length in create_direct_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/727e1f569855df83579edbd73dcb4a0723543a12
generic

vdpa/mlx5: Fix buffer length in create_direct_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c8a9f7bc00301e533a5366384f3070a8e7f8430

Vendor Advisories for CVE-2026-74712(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 43× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 02:59 UTCEG score recompute
  2. 2026-08-30 02:59 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 22:37 UTCGHSA enrichment
  5. 2026-08-29 18:15 UTCGHSA enrichment
  6. 2026-08-29 13:52 UTCGHSA enrichment
  7. 2026-08-29 09:29 UTCGHSA enrichment
  8. 2026-08-29 05:04 UTCGHSA enrichment
  9. 2026-08-29 00:39 UTCEG score recompute
  10. 2026-08-29 00:39 UTCGHSA enrichment
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 18:02 UTCGHSA enrichment
  13. 2026-08-28 13:33 UTCGHSA enrichment
  14. 2026-08-28 09:10 UTCGHSA enrichment
  15. 2026-08-28 04:48 UTCGHSA enrichment
  16. 2026-08-28 00:26 UTCGHSA enrichment
  17. 2026-08-27 20:02 UTCGHSA enrichment
  18. 2026-08-27 15:40 UTCEG score recompute
  19. 2026-08-27 15:40 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-27 11:17 UTCGHSA enrichment
  22. 2026-08-27 06:55 UTCGHSA enrichment
  23. 2026-08-27 02:33 UTCGHSA enrichment
  24. 2026-08-26 22:11 UTCGHSA enrichment
  25. 2026-08-26 17:50 UTCEG score recompute
Show 21 more
  1. 2026-08-26 17:49 UTCGHSA enrichment
  2. 2026-08-26 14:47 UTCEPSS rescore
  3. 2026-08-26 13:07 UTCGHSA enrichment
  4. 2026-08-26 08:40 UTCGHSA enrichment
  5. 2026-08-26 04:18 UTCGHSA enrichment
  6. 2026-08-25 23:55 UTCGHSA enrichment
  7. 2026-08-25 19:33 UTCGHSA enrichment
  8. 2026-08-25 15:12 UTCEG score recompute
  9. 2026-08-25 15:12 UTCGHSA enrichment
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-25 10:50 UTCEG score recompute
  12. 2026-08-25 10:50 UTCGHSA enrichment
  13. 2026-08-25 06:29 UTCEG score recompute
  14. 2026-08-25 06:29 UTCGHSA enrichment
  15. 2026-08-25 05:55 UTCEG score recompute▲ 9.30
  16. 2026-08-25 05:55 UTCGHSA enrichment
  17. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 9.3 · severity → CRITICAL
  18. 2026-08-24 14:18 UTCEPSS rescore
  19. 2026-08-22 16:24 UTCNVD update
  20. 2026-08-22 15:38 UTCEG score recompute
  21. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74712?
CVE-2026-74712 is a critical vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: vdpa/mlx5: Fix buffer length in createdirectkeys() We have seen in our CI the following KASAN message: BUG: KASAN: slab-out-of-bounds in cmdexec+0x550/0xca0 [mlx5core] Read of size 272 at addr 0000000176795020 by task…
When was CVE-2026-74712 disclosed?
CVE-2026-74712 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74712 actively exploited?
CVE-2026-74712 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74712?
CVE-2026-74712 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-74712?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74712, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74712

Explore →

Is Your Infrastructure Affected by CVE-2026-74712?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs