In the Linux kernel, the following vulnerability has been resolved: iommufd: Use sizeof(hdr) instead of sizeof(hdr) in veventq read The bound-check… (CVE-2026-64293)
A vulnerability in the Linux kernel's iommufd component involves an incorrect size check in the veventq read function. The code uses sizeof(hdr), which measures the pointer size, instead of sizeof(*hdr), the size of the actual structure, causing an undercount on 32-bit systems. This can lead to copying more data than the buffer can hold, potentially resulting in a buffer overflow. The issue is latent on 64-bit systems if the structure size grows beyond pointer size. The vulnerability has been resolved by correcting the size check to use sizeof(*hdr).
AI Analysis
Technical Summary
The Linux kernel's iommufd_veventq_fops_read() function incorrectly uses sizeof(hdr) (pointer size) instead of sizeof(*hdr) (structure size) for bound checking the vEVENT header. On 32-bit systems, this causes the check to undercount the header size by 4 bytes, allowing a copy operation to write beyond the user buffer, leading to a potential buffer overflow. On 64-bit systems, the issue currently does not manifest due to pointer and structure sizes matching, but remains a latent bug if the structure grows. The fix replaces sizeof(hdr) with sizeof(*hdr) to ensure correct bounds checking.
Potential Impact
On 32-bit architectures, this vulnerability can cause a buffer overflow in the kernel when reading vEVENT data, potentially leading to memory corruption or kernel instability. The issue does not currently affect 64-bit systems but could become problematic if the structure size increases. No known exploits are reported in the wild.
Mitigation Recommendations
A fix is available that corrects the size check to use sizeof(*hdr) instead of sizeof(hdr). Users and maintainers should apply the official Linux kernel patch that addresses this issue. Since this is a kernel vulnerability, updating to a patched kernel version is the recommended remediation. No alternative mitigations are specified.
In the Linux kernel, the following vulnerability has been resolved: iommufd: Use sizeof(hdr) instead of sizeof(hdr) in veventq read The bound-check… (CVE-2026-64293)
Description
A vulnerability in the Linux kernel's iommufd component involves an incorrect size check in the veventq read function. The code uses sizeof(hdr), which measures the pointer size, instead of sizeof(*hdr), the size of the actual structure, causing an undercount on 32-bit systems. This can lead to copying more data than the buffer can hold, potentially resulting in a buffer overflow. The issue is latent on 64-bit systems if the structure size grows beyond pointer size. The vulnerability has been resolved by correcting the size check to use sizeof(*hdr).
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's iommufd_veventq_fops_read() function incorrectly uses sizeof(hdr) (pointer size) instead of sizeof(*hdr) (structure size) for bound checking the vEVENT header. On 32-bit systems, this causes the check to undercount the header size by 4 bytes, allowing a copy operation to write beyond the user buffer, leading to a potential buffer overflow. On 64-bit systems, the issue currently does not manifest due to pointer and structure sizes matching, but remains a latent bug if the structure grows. The fix replaces sizeof(hdr) with sizeof(*hdr) to ensure correct bounds checking.
Potential Impact
On 32-bit architectures, this vulnerability can cause a buffer overflow in the kernel when reading vEVENT data, potentially leading to memory corruption or kernel instability. The issue does not currently affect 64-bit systems but could become problematic if the structure size increases. No known exploits are reported in the wild.
Mitigation Recommendations
A fix is available that corrects the size check to use sizeof(*hdr) instead of sizeof(hdr). Users and maintainers should apply the official Linux kernel patch that addresses this issue. Since this is a kernel vulnerability, updating to a patched kernel version is the recommended remediation. No alternative mitigations are specified.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rq5j-2985-g74r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64293"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f8086303
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:38:51 UTC
Last updated: 07/26/2026, 00:51:56 UTC
Views: 2
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.