| 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-50093: thermal: intel: int340x: processor: Fix warning during module unload |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| thermal: intel: int340x: processor: Fix warning during module unload |
| |
| The processor_thermal driver uses pcim_device_enable() to enable a PCI |
| device, which means the device will be automatically disabled on driver |
| detach. Thus there is no need to call pci_disable_device() again on it. |
| |
| With recent PCI device resource management improvements, e.g. commit |
| f748a07a0b64 ("PCI: Remove legacy pcim_release()"), this problem is |
| exposed and triggers the warining below. |
| |
| [ 224.010735] proc_thermal_pci 0000:00:04.0: disabling already-disabled device |
| [ 224.010747] WARNING: CPU: 8 PID: 4442 at drivers/pci/pci.c:2250 pci_disable_device+0xe5/0x100 |
| ... |
| [ 224.010844] Call Trace: |
| [ 224.010845] <TASK> |
| [ 224.010847] ? show_regs+0x6d/0x80 |
| [ 224.010851] ? __warn+0x8c/0x140 |
| [ 224.010854] ? pci_disable_device+0xe5/0x100 |
| [ 224.010856] ? report_bug+0x1c9/0x1e0 |
| [ 224.010859] ? handle_bug+0x46/0x80 |
| [ 224.010862] ? exc_invalid_op+0x1d/0x80 |
| [ 224.010863] ? asm_exc_invalid_op+0x1f/0x30 |
| [ 224.010867] ? pci_disable_device+0xe5/0x100 |
| [ 224.010869] ? pci_disable_device+0xe5/0x100 |
| [ 224.010871] ? kfree+0x21a/0x2b0 |
| [ 224.010873] pcim_disable_device+0x20/0x30 |
| [ 224.010875] devm_action_release+0x16/0x20 |
| [ 224.010878] release_nodes+0x47/0xc0 |
| [ 224.010880] devres_release_all+0x9f/0xe0 |
| [ 224.010883] device_unbind_cleanup+0x12/0x80 |
| [ 224.010885] device_release_driver_internal+0x1ca/0x210 |
| [ 224.010887] driver_detach+0x4e/0xa0 |
| [ 224.010889] bus_remove_driver+0x6f/0xf0 |
| [ 224.010890] driver_unregister+0x35/0x60 |
| [ 224.010892] pci_unregister_driver+0x44/0x90 |
| [ 224.010894] proc_thermal_pci_driver_exit+0x14/0x5f0 [processor_thermal_device_pci] |
| ... |
| [ 224.010921] ---[ end trace 0000000000000000 ]--- |
| |
| Remove the excess pci_disable_device() calls. |
| |
| [ rjw: Subject and changelog edits ] |
| |
| The Linux kernel CVE team has assigned CVE-2024-50093 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.14 with commit acd65d5d1cf4a3324c8970ba74632abe069fe23e and fixed in 5.15.168 with commit 8403021b6f32d68a7e3a6b8428ecaf5c153a9974 |
| Issue introduced in 5.14 with commit acd65d5d1cf4a3324c8970ba74632abe069fe23e and fixed in 6.1.113 with commit b4ab78f4adeaf6c98be5d375518dd4fb666eac5e |
| Issue introduced in 5.14 with commit acd65d5d1cf4a3324c8970ba74632abe069fe23e and fixed in 6.6.57 with commit dd64ea03375618684477f946be4f5e253f8676c2 |
| Issue introduced in 5.14 with commit acd65d5d1cf4a3324c8970ba74632abe069fe23e and fixed in 6.11.4 with commit 434525a864136c928b54fd2512b4c0167c207463 |
| Issue introduced in 5.14 with commit acd65d5d1cf4a3324c8970ba74632abe069fe23e and fixed in 6.12 with commit 99ca0b57e49fb73624eede1c4396d9e3d10ccf14 |
| |
| 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-50093 |
| 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/thermal/intel/int340x_thermal/processor_thermal_device_pci.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/8403021b6f32d68a7e3a6b8428ecaf5c153a9974 |
| https://git.kernel.org/stable/c/b4ab78f4adeaf6c98be5d375518dd4fb666eac5e |
| https://git.kernel.org/stable/c/dd64ea03375618684477f946be4f5e253f8676c2 |
| https://git.kernel.org/stable/c/434525a864136c928b54fd2512b4c0167c207463 |
| https://git.kernel.org/stable/c/99ca0b57e49fb73624eede1c4396d9e3d10ccf14 |
