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

kernel: btrfs: unlock inode and extent in caller when io_uring read extent fails

متن اصلی

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

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

بهره‌برداری

CVE-2026-98961

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

FIRST EPSS · ۱۴۰۵/۰۸/۳۰

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: unlock inode and extent in caller when io_uring read extent fails btrfs_uring_read_extent() runs only after btrfs_encoded_read() has taken the inode shared lock and the extent lock. On failure it used to unlock in out_fail, and a pages-array allocation failure returned -ENOMEM without unlocking at all. Unlock in the caller instead on all failure returns, matching the copy_to_user() error path. The deferred -EIOCBQUEUED path still unlocks in btrfs_uring_read_finished().

A flaw was found in the Linux kernel's Btrfs file system. A local attacker can cause a Denial of Service (DoS) by triggering error conditions during asynchronous read operations. When an io_uring read request fails, such as during a memory allocation failure, the kernel does not release acquired internal file locks. This failure results in a deadlock that freezes file system operations and leaves the system unresponsive.