CVE-2026-64496

published 25 Jul 2026 · updated 17 Nov 2026

iio: event: Fix event FIFO reset race

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.261, Kernel 5.15.212, Kernel 6.1.178 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: iio: event: Fix event FIFO reset race `iio_event_getfd()` creates the event file descriptor with `anon_inode_getfd()`, which allocates a new fd, creates the anonymous file and installs it in the process fd table before returning to the caller. The IIO code resets the event FIFO after `anon_inode_getfd()` has returned, but before `IIO_GET_EVENT_FD_IOCTL` has copied the fd number to userspace. But since fd tables are shared between threads, another thread can guess the newly allocated fd number and issue a `read()` on it as soon as the fd has been installed. This means the `kfifo_to_user()` in `iio_event_chrdev_read()` can run in parallel with the `kfifo_reset_out()` in `iio_event_getfd()`. The kfifo documentation says that `kfifo_reset_out()` is only safe when it is called from the reader thread and there is only one concurrent reader. Otherwise it is dangerous and must be handled in the same way as `kfifo_reset()`. If that happens, `kfifo_to_user()` can advance the FIFO `out` index based on state from before the reset, after the reset has already moved the `out` index to the current `in` index. That can leave the FIFO with an `out` index past the `in` index. A later `read()` can then see an underflowed FIFO length and copy more data than the event FIFO buffer contains. This can result in an out-of-bounds read and leak adjacent kernel memory to userspace. Move the FIFO reset before `anon_inode_getfd()`. At that point the event fd is marked busy, but the new fd has not been installed yet, so userspace cannot access it while the FIFO is reset.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3.15 <5.10.261, >=5.11 <5.15.212, >=5.16 <6.1.178, >=6.13 <6.18.39, >=6.19 <7.1.4, >=6.2 <6.6.145, >=6.7 <6.12.96, =7.2, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <72c6aa8e0d74eab91b8694cde97dec088c248fee, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <9dc84ba4be5bbeb29ee49efe6cea2cb32c461424, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <9edefd4c56bee3fe331e0355d1f10a533134999d, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <a13ef1adbc62085b21b546b07b0be7e2fbf52150, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <af791d295737ea6b6ff2c8d8488462a49c14af01, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <d16a702ca7d29c0b7a9b509339d1b044a1cadb32, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <f187dc5a4c4846ffa07d9bda6e760837ed005574, =3.15, >=b91accafbb1031b80d22ad83576877ff2f8b4774 <0d4a646d7f87ea3625fafe387043fddc6a2f5e7f5.10.261, 5.15.212, 6.1.178, 6.18.39, 7.1.4, 6.6.145, 6.12.96, 72c6aa8e0d74eab91b8694cde97dec088c248fee, 9dc84ba4be5bbeb29ee49efe6cea2cb32c461424, 9edefd4c56bee3fe331e0355d1f10a533134999d, a13ef1adbc62085b21b546b07b0be7e2fbf52150, af791d295737ea6b6ff2c8d8488462a49c14af01, d16a702ca7d29c0b7a9b509339d1b044a1cadb32, f187dc5a4c4846ffa07d9bda6e760837ed005574, 0d4a646d7f87ea3625fafe387043fddc6a2f5e7f
linux-kernel: Kernel>=3.15.0 <5.10.261, >=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.39, >=6.19.0 <7.1.4, >=6.2.0 <6.6.145, >=6.7.0 <6.12.965.10.261, 5.15.212, 6.1.178, 6.18.39, 7.1.4, 6.6.145, 6.12.96

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64496 severity on Zeptric[![CVE-2026-64496](https://zeptric.io/badge/cve/CVE-2026-64496.svg)](https://zeptric.io/cve/CVE-2026-64496)