همهٔ گزارش‌ها
متوسط

kernel: fuse: fix missing barrier when checking io-uring readiness

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-80859

احتمال بهره‌برداری در ۳۰ روز آینده: 0.16%

FIRST EPSS · ۱۴۰۵/۰۸/۲۹

شرح آسیب‌پذیری

In the Linux kernel, the following vulnerability has been resolved: fuse: fix missing barrier when checking io-uring readiness fuse_block_alloc() reads fch->initialized and then fch->io_uring. fch->io_uring is set before fch->initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads. This may lead a CPU to observe fch->initialized=1 but fch->io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents. Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.

A flaw was found in the Linux kernel's FUSE (Filesystem in Userspace) subsystem. A missing memory barrier when checking the readiness of io-uring queues could allow a CPU to observe an inconsistent state. This inconsistency can bypass a critical check, potentially reintroducing a lock-order inversion deadlock. Such a deadlock could lead to a system hang or Denial of Service.