Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64496: iio: event: Fix event FIFO reset race

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0d4a646d7f87ea3625fafe387043fddc6a2f5e7f, 72c6aa8e0d74eab91b8694cde97dec088c248fee, 9dc84ba4be5bbeb29ee49efe6cea2cb32c461424; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 0d4a646d7f87ea3625fafe387043fddc6a2f5e7f, 72c6aa8e0d74eab91b8694cde97dec088c248fee, 9dc84ba4be5bbeb29ee49efe6cea2cb32c461424; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Nov 3, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64496

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.15affected
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before 9dc84ba4be5bbeb29ee49efe6cea2cb32c461424affected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before d16a702ca7d29c0b7a9b509339d1b044a1cadb32affected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before a13ef1adbc62085b21b546b07b0be7e2fbf52150affected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before 0d4a646d7f87ea3625fafe387043fddc6a2f5e7faffected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before 72c6aa8e0d74eab91b8694cde97dec088c248feeaffected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before 9edefd4c56bee3fe331e0355d1f10a533134999daffected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before f187dc5a4c4846ffa07d9bda6e760837ed005574affected · git
    • b91accafbb1031b80d22ad83576877ff2f8b4774 and later · before af791d295737ea6b6ff2c8d8488462a49c14af01affected · git
    • before 3.15not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.154.1.el8_104.18.0-553.154.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.154.1.rt7.495.el8_104.18.0-553.154.1.rt7.495.el8_10

+66

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-64494Jul 25, 2026 · iio: light: gp2ap002: fix runtime PM leak on read error
    0Monitor
  • ← EarlierCVE-2026-64495Jul 25, 2026 · iio: gyro: bmg160: bail out when bandwidth/filter is not in table
    0Monitor
  • Later →CVE-2026-64497Jul 25, 2026 · iio: chemical: scd30: Cleanup initializations and fix sign-extension bug
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0d4a646d7f87ea3625fafe387043fddc6a2f5e7fVendor (CNA)
Linux Linux72c6aa8e0d74eab91b8694cde97dec088c248feeVendor (CNA)
Linux Linux9dc84ba4be5bbeb29ee49efe6cea2cb32c461424Vendor (CNA)
Linux Linux9edefd4c56bee3fe331e0355d1f10a533134999dVendor (CNA)
Linux Linuxa13ef1adbc62085b21b546b07b0be7e2fbf52150Vendor (CNA)
Linux Linuxaf791d295737ea6b6ff2c8d8488462a49c14af01Vendor (CNA)
Linux Linuxd16a702ca7d29c0b7a9b509339d1b044a1cadb32Vendor (CNA)
Linux Linuxf187dc5a4c4846ffa07d9bda6e760837ed005574Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.154.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.154.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.154.1.rt7.495.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.154.1.rt7.495.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+7

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-639786 days apartnet/handshake: Drain pending requests at net namespace exit
    39Monitor
  • CVE-2026-7206421 days apartnet: mana: Sync page pool RX frags for CPU
    39Monitor
  • CVE-2026-6456110 days apartKVM: x86: Check for invalid/obsolete root *after* making MMU pages available
    35Monitor
  • CVE-2026-6832916 days apartiommu/amd: Wait for completion instead of returning early in iommu_completion_wait()
    35Monitor
  • CVE-2026-645604 days apartposix-cpu-timers: Prevent UAF caused by non-leader exec() race
    31Monitor
  • CVE-2026-639776 days apartdpll: zl3073x: use __dpll_device_change_ntf() and remove change_work
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records