| 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-56723: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices |
| |
| While design wise the idea of converting the driver to use |
| the hierarchy of the IRQ chips is correct, the implementation |
| has (inherited) flaws. This was unveiled when platform_get_irq() |
| had started WARN() on IRQ 0 that is supposed to be a Linux |
| IRQ number (also known as vIRQ). |
| |
| Rework the driver to respect IRQ domain when creating each MFD |
| device separately, as the domain is not the same for all of them. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56723 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 5.4.287 with commit 6ea17c03edc7ed0aabb1431eb26e2f94849af68a |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 5.10.231 with commit 61d590d7076b50b6ebdea1f3b83bb041c01fc482 |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 5.15.174 with commit bb6642d4b3136359b5b620049f76515876e6127e |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 6.1.120 with commit 7ba45b8bc62e64da524d45532107ae93eb33c93c |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 6.6.64 with commit d4cc78bd6a25accb7ae2ac9fc445d1e1deda4a62 |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 6.11.11 with commit 897713c9d24f6ec394585abfcf259a6e5cad22c8 |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 6.12.2 with commit b3d45c19bcffb9a9a821df759f60be39d88c19f4 |
| Issue introduced in 4.13 with commit 57129044f5044dcd73c22d91491906104bd331fd and fixed in 6.13 with commit 0350d783ab888cb1cb48ced36cc28b372723f1a4 |
| |
| 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-56723 |
| 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/mfd/intel_soc_pmic_bxtwc.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/6ea17c03edc7ed0aabb1431eb26e2f94849af68a |
| https://git.kernel.org/stable/c/61d590d7076b50b6ebdea1f3b83bb041c01fc482 |
| https://git.kernel.org/stable/c/bb6642d4b3136359b5b620049f76515876e6127e |
| https://git.kernel.org/stable/c/7ba45b8bc62e64da524d45532107ae93eb33c93c |
| https://git.kernel.org/stable/c/d4cc78bd6a25accb7ae2ac9fc445d1e1deda4a62 |
| https://git.kernel.org/stable/c/897713c9d24f6ec394585abfcf259a6e5cad22c8 |
| https://git.kernel.org/stable/c/b3d45c19bcffb9a9a821df759f60be39d88c19f4 |
| https://git.kernel.org/stable/c/0350d783ab888cb1cb48ced36cc28b372723f1a4 |
