Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-74712

9.3 · CRITICAL

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-o…

Published Aug 22, 2026EPSS 0.14%

Overview

CVE-2026-74712 is a critical-severity vulnerability. It was published on August 22, 2026 and has a CVSS 3.1 base score of 9.3 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.3, rated CRITICAL. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical 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' fiel

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/6c8a9f7bc00301e533a5366384f3070a8e7f8430Refgit.kernel.org/stable/c/727e1f569855df83579edbd73dcb4a0723543a12Refgit.kernel.org/stable/c/cde8931a25392670dd59a0acfcab87a830ab66c5Refgit.kernel.org/stable/c/ec3bb289cf19d526224117d5d450a5fd9cbd5ab2

How CyberStrike helps

Frequently asked questions

What is CVE-2026-74712?

CVE-2026-74712 is a critical-severity vulnerability. It was published on August 22, 2026 and has a CVSS 3.1 base score of 9.3 (CRITICAL).

How severe is CVE-2026-74712?

This vulnerability has a CVSS 3.1 base score of 9.3, rated CRITICAL. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-74712?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-74712?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-74712 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999