| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-53184: um: ubd: Do not use drvdata in release |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| um: ubd: Do not use drvdata in release |
| |
| The drvdata is not available in release. Let's just use container_of() |
| to get the ubd instance. Otherwise, removing a ubd device will result |
| in a crash: |
| |
| RIP: 0033:blk_mq_free_tag_set+0x1f/0xba |
| RSP: 00000000e2083bf0 EFLAGS: 00010246 |
| RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00 |
| RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348 |
| RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7 |
| R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000 |
| R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0 |
| Kernel panic - not syncing: Segfault with no mm |
| CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1 |
| Workqueue: events mc_work_proc |
| Stack: |
| 00000000 604f7ef0 62c5d000 62405d20 |
| e2083c30 6002c776 6002c755 600e47ff |
| e2083c60 6025ffe3 04208060 603d36e0 |
| Call Trace: |
| [<6002c776>] ubd_device_release+0x21/0x55 |
| [<6002c755>] ? ubd_device_release+0x0/0x55 |
| [<600e47ff>] ? kfree+0x0/0x100 |
| [<6025ffe3>] device_release+0x70/0xba |
| [<60381d6a>] kobject_put+0xb5/0xe2 |
| [<6026027b>] put_device+0x19/0x1c |
| [<6026a036>] platform_device_put+0x26/0x29 |
| [<6026ac5a>] platform_device_unregister+0x2c/0x2e |
| [<6002c52e>] ubd_remove+0xb8/0xd6 |
| [<6002bb74>] ? mconsole_reply+0x0/0x50 |
| [<6002b926>] mconsole_remove+0x160/0x1cc |
| [<6002bbbc>] ? mconsole_reply+0x48/0x50 |
| [<6003379c>] ? um_set_signals+0x3b/0x43 |
| [<60061c55>] ? update_min_vruntime+0x14/0x70 |
| [<6006251f>] ? dequeue_task_fair+0x164/0x235 |
| [<600620aa>] ? update_cfs_group+0x0/0x40 |
| [<603a0e77>] ? __schedule+0x0/0x3ed |
| [<60033761>] ? um_set_signals+0x0/0x43 |
| [<6002af6a>] mc_work_proc+0x77/0x91 |
| [<600520b4>] process_scheduled_works+0x1af/0x2c3 |
| [<6004ede3>] ? assign_work+0x0/0x58 |
| [<600527a1>] worker_thread+0x2f7/0x37a |
| [<6004ee3b>] ? set_pf_worker+0x0/0x64 |
| [<6005765d>] ? arch_local_irq_save+0x0/0x2d |
| [<60058e07>] ? kthread_exit+0x0/0x3a |
| [<600524aa>] ? worker_thread+0x0/0x37a |
| [<60058f9f>] kthread+0x130/0x135 |
| [<6002068e>] new_thread_handler+0x85/0xb6 |
| |
| The Linux kernel CVE team has assigned CVE-2024-53184 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 4.19.325 with commit 23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8 |
| Fixed in 5.4.287 with commit 300e277e463e6326938dd55ea560eafa0f5c88a5 |
| Fixed in 5.10.231 with commit 509ba8746f812e45a05034ba18b73db574693d11 |
| Fixed in 5.15.174 with commit 5727343348f34e11a7c5a2a944d5aa505731d876 |
| Fixed in 6.1.120 with commit a5a75207efae4b558aaa34c288de7d6f2e926b4b |
| Fixed in 6.6.64 with commit 2d194d951895df214e066d08146e77cb6e02c1d4 |
| Fixed in 6.11.11 with commit e6e5a4cded9bef3a1b0a4fac815b7176eb9a18ec |
| Fixed in 6.12.2 with commit 16cf8511680809a9f20b3dd224c06d482648f9e2 |
| Fixed in 6.13 with commit 5bee35e5389f450a7eea7318deb9073e9414d3b1 |
| |
| 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-53184 |
| 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: |
| arch/um/drivers/ubd_kern.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/23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8 |
| https://git.kernel.org/stable/c/300e277e463e6326938dd55ea560eafa0f5c88a5 |
| https://git.kernel.org/stable/c/509ba8746f812e45a05034ba18b73db574693d11 |
| https://git.kernel.org/stable/c/5727343348f34e11a7c5a2a944d5aa505731d876 |
| https://git.kernel.org/stable/c/a5a75207efae4b558aaa34c288de7d6f2e926b4b |
| https://git.kernel.org/stable/c/2d194d951895df214e066d08146e77cb6e02c1d4 |
| https://git.kernel.org/stable/c/e6e5a4cded9bef3a1b0a4fac815b7176eb9a18ec |
| https://git.kernel.org/stable/c/16cf8511680809a9f20b3dd224c06d482648f9e2 |
| https://git.kernel.org/stable/c/5bee35e5389f450a7eea7318deb9073e9414d3b1 |
