In the Linux kernel, the following vulnerability has been resolved: fuse: avoid 32-bit prune notification count wrap FUSE_NOTIFY_PRUNE validates the nodeid payload length with: size - sizeof(outarg) != outarg.count * sizeof(u64) On 32-bit kernels, size_t is also 32 bits, so the daemon-controlled count multiplication can wrap. A prune notification with count 0x20000000 and no nodeid payload passes the check, enters the copy loop, and asks the device copy path to read nodeids that are not present in the userspace write buffer. In QEMU this reaches the fuse_copy_fill() BUG_ON(!err) path. Validate the payload length with array_size() instead. That accepts exactly the same valid messages, but avoids wrapping arithmetic before the copy loop consumes the count.

A flaw was found in the Linux kernel's Filesystem in Userspace (FUSE) component. On 32-bit systems, an integer overflow vulnerability exists in the handling of `FUSE_NOTIFY_PRUNE` messages. A malicious FUSE daemon or a local user could craft a prune notification with a specific count, causing an integer overflow during payload length validation. This can lead to the kernel attempting to read non-existent data, resulting in a system crash and a Denial of Service (DoS).

Red Hat Enterprise Linux 10 Not affected kernel Red Hat Enterprise Linux 6 Out of support scope kernel Red Hat Enterprise Linux 7 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel-rt Red Hat Enterprise Linux 8 Not affected kernel Red Hat Enterprise Linux 8 Not affected kernel-rt Red Hat Enterprise Linux 9 Not affected kernel Red Hat Enterprise Linux 9 Not affected kernel-rt https://www.cve.org/CVERecord?id=CVE-2026-64267 https://nvd.nist.gov/vuln/detail/CVE-2026-64267 https://lore.kernel.org/linux-cve-announce/2026072559-CVE-2026-64267-a265@gregkh/T