| 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-2022-49099: Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register() |
| |
| Initialize the device's dma_{mask,parms} pointers and the device's |
| dma_mask value before invoking device_register(). Address the |
| following trace with 5.17-rc7: |
| |
| [ 49.646839] WARNING: CPU: 0 PID: 189 at include/linux/dma-mapping.h:543 |
| netvsc_probe+0x37a/0x3a0 [hv_netvsc] |
| [ 49.646928] Call Trace: |
| [ 49.646930] <TASK> |
| [ 49.646935] vmbus_probe+0x40/0x60 [hv_vmbus] |
| [ 49.646942] really_probe+0x1ce/0x3b0 |
| [ 49.646948] __driver_probe_device+0x109/0x180 |
| [ 49.646952] driver_probe_device+0x23/0xa0 |
| [ 49.646955] __device_attach_driver+0x76/0xe0 |
| [ 49.646958] ? driver_allows_async_probing+0x50/0x50 |
| [ 49.646961] bus_for_each_drv+0x84/0xd0 |
| [ 49.646964] __device_attach+0xed/0x170 |
| [ 49.646967] device_initial_probe+0x13/0x20 |
| [ 49.646970] bus_probe_device+0x8f/0xa0 |
| [ 49.646973] device_add+0x41a/0x8e0 |
| [ 49.646975] ? hrtimer_init+0x28/0x80 |
| [ 49.646981] device_register+0x1b/0x20 |
| [ 49.646983] vmbus_device_register+0x5e/0xf0 [hv_vmbus] |
| [ 49.646991] vmbus_add_channel_work+0x12d/0x190 [hv_vmbus] |
| [ 49.646999] process_one_work+0x21d/0x3f0 |
| [ 49.647002] worker_thread+0x4a/0x3b0 |
| [ 49.647005] ? process_one_work+0x3f0/0x3f0 |
| [ 49.647007] kthread+0xff/0x130 |
| [ 49.647011] ? kthread_complete_and_exit+0x20/0x20 |
| [ 49.647015] ret_from_fork+0x22/0x30 |
| [ 49.647020] </TASK> |
| [ 49.647021] ---[ end trace 0000000000000000 ]--- |
| |
| The Linux kernel CVE team has assigned CVE-2022-49099 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.17 with commit 743b237c3a7b0f5b44aa704aae8a1058877b6322 and fixed in 5.17.3 with commit 2fe4b8631427618175a32f125062df91a5fe3f73 |
| Issue introduced in 5.17 with commit 743b237c3a7b0f5b44aa704aae8a1058877b6322 and fixed in 5.18 with commit 3a5469582c241abca22500f36a9cb8e9331969cf |
| |
| 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-2022-49099 |
| 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/hv/vmbus_drv.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/2fe4b8631427618175a32f125062df91a5fe3f73 |
| https://git.kernel.org/stable/c/3a5469582c241abca22500f36a9cb8e9331969cf |
