{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-30T01:26:57.454","vulnerabilities":[{"cve":{"id":"CVE-2023-53848","sourceIdentifier":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","published":"2025-12-09T16:17:25.290","lastModified":"2026-04-15T00:35:42.020","vulnStatus":"Deferred","cveTags":[],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid5-cache: fix a deadlock in r5l_exit_log()\n\nCommit b13015af94cf (\"md/raid5-cache: Clear conf->log after finishing\nwork\") introduce a new problem:\n\n// caller hold reconfig_mutex\nr5l_exit_log\n flush_work(&log->disable_writeback_work)\n\t\t\tr5c_disable_writeback_async\n\t\t\t wait_event\n\t\t\t  /*\n\t\t\t   * conf->log is not NULL, and mddev_trylock()\n\t\t\t   * will fail, wait_event() can never pass.\n\t\t\t   */\n conf->log = NULL\n\nFix this problem by setting 'config->log' to NULL before wake_up() as it\nused to be, so that wait_event() from r5c_disable_writeback_async() can\nexist. In the meantime, move forward md_unregister_thread() so that\nnull-ptr-deref this commit fixed can still be fixed."}],"metrics":{},"references":[{"url":"https://git.kernel.org/stable/c/71cf23271f015a57038bdc4669952096f9fe5500","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a705b11b358dee677aad80630e7608b2d5f56691","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/ac9e103f282a7854f3274ef5ff0742fbbe8d7d6b","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/c406984738215dc20ac2dc63e49d70f20797730e","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}]}}]}