[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024111933-CVE-2024-53067-0c9e@gregkh>
Date: Tue, 19 Nov 2024 18:22:38 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53067: scsi: ufs: core: Start the RTC update work later
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: core: Start the RTC update work later
The RTC update work involves runtime resuming the UFS controller. Hence,
only start the RTC update work after runtime power management in the UFS
driver has been fully initialized. This patch fixes the following kernel
crash:
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Workqueue: events ufshcd_rtc_work
Call trace:
_raw_spin_lock_irqsave+0x34/0x8c (P)
pm_runtime_get_if_active+0x24/0x9c (L)
pm_runtime_get_if_active+0x24/0x9c
ufshcd_rtc_work+0x138/0x1b4
process_one_work+0x148/0x288
worker_thread+0x2cc/0x3d4
kthread+0x110/0x114
ret_from_fork+0x10/0x20
The Linux kernel CVE team has assigned CVE-2024-53067 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit 6bf999e0eb41 and fixed in 6.11.8 with commit 4c25f784fba8
Issue introduced in 6.8 with commit 6bf999e0eb41 and fixed in 6.12 with commit 54c814c8b23b
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-53067
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/ufs/core/ufshcd.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/4c25f784fba81227e0437337f962d34380d1c250
https://git.kernel.org/stable/c/54c814c8b23bc7617be3d46abdb896937695dbfa
Powered by blists - more mailing lists