| 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-49072: gpio: Restrict usage of GPIO chip irq members before initialization |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| gpio: Restrict usage of GPIO chip irq members before initialization |
| |
| GPIO chip irq members are exposed before they could be completely |
| initialized and this leads to race conditions. |
| |
| One such issue was observed for the gc->irq.domain variable which |
| was accessed through the I2C interface in gpiochip_to_irq() before |
| it could be initialized by gpiochip_add_irqchip(). This resulted in |
| Kernel NULL pointer dereference. |
| |
| Following are the logs for reference :- |
| |
| kernel: Call Trace: |
| kernel: gpiod_to_irq+0x53/0x70 |
| kernel: acpi_dev_gpio_irq_get_by+0x113/0x1f0 |
| kernel: i2c_acpi_get_irq+0xc0/0xd0 |
| kernel: i2c_device_probe+0x28a/0x2a0 |
| kernel: really_probe+0xf2/0x460 |
| kernel: RIP: 0010:gpiochip_to_irq+0x47/0xc0 |
| |
| To avoid such scenarios, restrict usage of GPIO chip irq members before |
| they are completely initialized. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49072 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.111 with commit 7e88a50704b0c49ad3f2d11e8b963341cf68a89f |
| Fixed in 5.15.34 with commit 0912cf021fb5749372b3782611d8b1de4986c13a |
| Fixed in 5.16.20 with commit 2c1fa3614795e2b24da1ba95de0b27b8f6ea4537 |
| Fixed in 5.17.3 with commit f8dea54f74cae8c2e4d7b2952e8fed7743a85c87 |
| Fixed in 5.18 with commit 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 |
| |
| 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-49072 |
| 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/gpio/gpiolib.c |
| include/linux/gpio/driver.h |
| |
| |
| 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/7e88a50704b0c49ad3f2d11e8b963341cf68a89f |
| https://git.kernel.org/stable/c/0912cf021fb5749372b3782611d8b1de4986c13a |
| https://git.kernel.org/stable/c/2c1fa3614795e2b24da1ba95de0b27b8f6ea4537 |
| https://git.kernel.org/stable/c/f8dea54f74cae8c2e4d7b2952e8fed7743a85c87 |
| https://git.kernel.org/stable/c/5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 |
