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… (CVE-2026-74712)
A vulnerability in the Linux kernel's vdpa/mlx5 driver was identified and resolved. The issue involved an out-of-bounds read caused by incorrect buffer length calculation in the create_direct_keys() function. Specifically, the function miscalculated the input buffer size, leading to a read beyond the allocated memory when copying command data. This flaw was detected through kernel address sanitizer (KASAN) messages during continuous integration testing.
AI Analysis
Technical Summary
The Linux kernel vdpa/mlx5 driver contained a vulnerability where create_direct_keys() incorrectly calculated the buffer length for input data. The function's size calculation included the entire structure (out + in + mtt[]), but the pointer passed to cmd_exec pointed only to the 'in' field, skipping the 'out' field. This mismatch caused mlx5_copy_to_msg() to read beyond the allocated buffer by the size of the 'out' field, resulting in a slab-out-of-bounds read. The issue was identified via KASAN reports and fixed by properly calculating the input size to match the pointer and allocation size.
Potential Impact
The vulnerability causes a read beyond the allocated buffer in kernel space, which can lead to memory corruption or kernel instability. While no direct exploit in the wild is known, such out-of-bounds reads can potentially be leveraged for denial of service or information disclosure under certain conditions.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the buffer length calculation in create_direct_keys(). Users should update to the fixed kernel version once available. Patch status is not yet confirmed from vendor advisory; check the official Linux kernel repositories or advisories for the specific patch and update guidance.
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… (CVE-2026-74712)
Description
A vulnerability in the Linux kernel's vdpa/mlx5 driver was identified and resolved. The issue involved an out-of-bounds read caused by incorrect buffer length calculation in the create_direct_keys() function. Specifically, the function miscalculated the input buffer size, leading to a read beyond the allocated memory when copying command data. This flaw was detected through kernel address sanitizer (KASAN) messages during continuous integration testing.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vdpa/mlx5 driver contained a vulnerability where create_direct_keys() incorrectly calculated the buffer length for input data. The function's size calculation included the entire structure (out + in + mtt[]), but the pointer passed to cmd_exec pointed only to the 'in' field, skipping the 'out' field. This mismatch caused mlx5_copy_to_msg() to read beyond the allocated buffer by the size of the 'out' field, resulting in a slab-out-of-bounds read. The issue was identified via KASAN reports and fixed by properly calculating the input size to match the pointer and allocation size.
Potential Impact
The vulnerability causes a read beyond the allocated buffer in kernel space, which can lead to memory corruption or kernel instability. While no direct exploit in the wild is known, such out-of-bounds reads can potentially be leveraged for denial of service or information disclosure under certain conditions.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the buffer length calculation in create_direct_keys(). Users should update to the fixed kernel version once available. Patch status is not yet confirmed from vendor advisory; check the official Linux kernel repositories or advisories for the specific patch and update guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8f7v-7fr8-r5c3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74712"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f0acd9273b499bc6f3
Added to database: 08/22/2026, 22:51:28 UTC
Last enriched: 08/23/2026, 00:54:48 UTC
Last updated: 08/23/2026, 02:32:07 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.