In the Linux kernel, the following vulnerability has been resolved: iommufd: Use sizeof(*hdr) instead of sizeof(hdr) in veventq read The bound-check in iommufd_veventq_fops_read() for the normal vEVENT path uses sizeof(hdr) where the surrounding code uses sizeof(*hdr): if (!vevent_for_lost_events_header(cur) && sizeof(hdr) + cur->data_len > count - done) { hdr is declared as struct iommufd_vevent_header *, so sizeof(hdr) evaluates to the size of the pointer. Surrounding code uses sizeof(*hdr) consistently: if (done >= count || sizeof(*hdr) > count - done) { ... if (copy_to_user(buf + done, hdr, sizeof(*hdr))) { ... done += sizeof(*hdr); struct iommufd_vevent_header is currently 8 bytes (two __u32 fields, flags and sequence), so on 64-bit (sizeof(void *) == 8) the two expressions happen to be equal and the check works as intended. On 32-bit (sizeof(void *) == 4) the check under-counts the header by 4 bytes: a vEVENT whose data_len causes 8 + cur->data_len to exceed co
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-64293 is a buffer overflow vulnerability in the Linux kernel's iommufd (IOMMU File Descriptor) subsystem, specifically in the virtual event queue read operation. The flaw stems from a sizeof() operator misuse where sizeof(hdr) returns the size of a pointer rather than the actual structure, causing inadequate bounds checking. This allows an attacker with access to iommufd operations to write beyond allocated buffer boundaries, potentially leading to kernel memory corruption, privilege escalation, or denial of service. Systems running vulnerable Linux kernels with iommufd enabled are affected, particularly those relying on IOMMU virtualization for nested guest support or device passthrough scenarios.
Casky.ai's Claude-powered analysis engine would detect attack patterns associated with this vulnerability by identifying memory manipulation techniques mapped to MITRE ATT&CK's Execution and Privilege Escalation tactics. Practitioners using Casky would see findings related to improper input validation (CWE-119 class), suspicious kernel memory access patterns, and potential exploitation chains leveraging T1548 (Abuse Elevation Control Mechanism) or T1611 (Escape to Host) if containerized. The platform's 754 security skills would flag suspicious iommufd syscall sequences, abnormal buffer operations, and attempts to trigger the sizeof() logic error—enabling defenders to identify exploitation attempts before kernel compromise occurs.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-64293. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation