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

kernel: md/raid5-cache: fix a deadlock in r5l_exit_log()

متن اصلی

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

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

بهره‌برداری

CVE-2023-53848

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

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

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

In the Linux kernel, the following vulnerability has been resolved: md/raid5-cache: fix a deadlock in r5l_exit_log() Commit b13015af94cf ("md/raid5-cache: Clear conf->log after finishing work") introduce a new problem: // caller hold reconfig_mutex r5l_exit_log flush_work(&log->disable_writeback_work) r5c_disable_writeback_async wait_event /*

  • conf->log is not NULL, and mddev_trylock()

  • will fail, wait_event() can never pass. */ conf->log = NULL Fix this problem by setting 'config->log' to NULL before wake_up() as it used to be, so that wait_event() from r5c_disable_writeback_async() can exist. In the meantime, move forward md_unregister_thread() so that null-ptr-deref this commit fixed can still be fixed.

A deadlock vulnerability was found in the md RAID5 cache (r5l) subsystem in the Linux kernel. In r5l_exit_log(), flush_work() is called while holding reconfig_mutex, which waits for disable_writeback_work to complete. However, r5c_disable_writeback_async() calls wait_event() which requires conf->log to be NULL, but that only happens after flush_work() returns, creating a deadlock.