CVE-2026-64588
Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
Detection and validation
Mapped metadata availability only. These signals do not change priority.
Sigma
Not mapped by tracked sources.
Atomic
Not mapped by tracked sources.
Nuclei
Not mapped by tracked sources.
What it is
ReportedIn the Linux kernel, the following vulnerability has been resolved: fuse-uring: fix data races on ring->ready On weakly-ordered architectures, the store to fiq->ops can be reordered past the store to ring->ready, allowing a CPU that sees ring->ready == true via fuse_uring_ready() to dispatch requests through a stale fiq->ops pointer. Upgrade the store to smp_store_release() and the load in fuse_uring_ready() to smp_load_acquire() so that the preceding WRITE_ONCE(fiq->ops, ...) is visible to any CPU that observes ring->ready == true.…
Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:
What is affected
ReportedLinux; Linux. Product-level identification only; no affected-version conclusion is available from this field.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
Urgency and basis
ReportedTrack · 115.2
Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:
Exploitation evidence
Not reportedNot reported by tracked sources.
What to do
Not reportedNot reported by tracked sources.
Evidence detail
Loading the full tracker evidence record…