CVE-2026-64588

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fuse-uring: fix data races on ring-&gt;ready<br /> <br /> On weakly-ordered architectures, the store to fiq-&gt;ops can be<br /> reordered past the store to ring-&gt;ready, allowing a CPU that sees<br /> ring-&gt;ready == true via fuse_uring_ready() to dispatch requests<br /> through a stale fiq-&gt;ops pointer. Upgrade the store to<br /> smp_store_release() and the load in fuse_uring_ready() to<br /> smp_load_acquire() so that the preceding WRITE_ONCE(fiq-&gt;ops, ...)<br /> is visible to any CPU that observes ring-&gt;ready == true.<br /> <br /> Additionally, fuse_uring_do_register() publishes ring-&gt;ready with<br /> WRITE_ONCE() but the fast-path check reads it with a plain load.<br /> This is a marked-vs-unmarked access that KCSAN will flag. Wrap it in<br /> READ_ONCE() to mark it without adding unnecessary ordering.<br /> <br /> Also wrap the fc-&gt;ring load in fuse_uring_ready() in READ_ONCE() to<br /> prevent the compiler from reloading it between the NULL check and the<br /> dereference.