Menu

Star on GitHub · 3.2k

CVE-2026-64293

7.8 · HIGH

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…

Published Jul 25, 2026EPSS 0.17%

Overview

CVE-2026-64293 is a high-severity vulnerability. It was published on July 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

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.

Frequently asked questions

What is CVE-2026-64293?

CVE-2026-64293 is a high-severity vulnerability. It was published on July 25, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64293?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

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-64293?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64293 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 HIGH CVEs from 2026

View all