| 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-44950: serial: sc16is7xx: fix invalid FIFO access with special register set |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| serial: sc16is7xx: fix invalid FIFO access with special register set |
| |
| When enabling access to the special register set, Receiver time-out and |
| RHR interrupts can happen. In this case, the IRQ handler will try to read |
| from the FIFO thru the RHR register at address 0x00, but address 0x00 is |
| mapped to DLL register, resulting in erroneous FIFO reading. |
| |
| Call graph example: |
| sc16is7xx_startup(): entry |
| sc16is7xx_ms_proc(): entry |
| sc16is7xx_set_termios(): entry |
| sc16is7xx_set_baud(): DLH/DLL = $009C --> access special register set |
| sc16is7xx_port_irq() entry --> IIR is 0x0C |
| sc16is7xx_handle_rx() entry |
| sc16is7xx_fifo_read(): --> unable to access FIFO (RHR) because it is |
| mapped to DLL (LCR=LCR_CONF_MODE_A) |
| sc16is7xx_set_baud(): exit --> Restore access to general register set |
| |
| Fix the problem by claiming the efr_lock mutex when accessing the Special |
| register set. |
| |
| The Linux kernel CVE team has assigned CVE-2024-44950 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 3.16 with commit dfeae619d781dee61666d5551b93ba3be755a86b and fixed in 6.1.120 with commit cc6a3f35bc9b3a8da1b195420a2e8d9fdadfa831 |
| Issue introduced in 3.16 with commit dfeae619d781dee61666d5551b93ba3be755a86b and fixed in 6.6.64 with commit dc5ead0e8fc5ef53b8553394d4aab60c277976b3 |
| Issue introduced in 3.16 with commit dfeae619d781dee61666d5551b93ba3be755a86b and fixed in 6.10.5 with commit 6a6730812220a9a5ce4003eb347da1ee5abd06b0 |
| Issue introduced in 3.16 with commit dfeae619d781dee61666d5551b93ba3be755a86b and fixed in 6.11 with commit 7d3b793faaab1305994ce568b59d61927235f57b |
| |
| 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-44950 |
| 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/tty/serial/sc16is7xx.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/cc6a3f35bc9b3a8da1b195420a2e8d9fdadfa831 |
| https://git.kernel.org/stable/c/dc5ead0e8fc5ef53b8553394d4aab60c277976b3 |
| https://git.kernel.org/stable/c/6a6730812220a9a5ce4003eb347da1ee5abd06b0 |
| https://git.kernel.org/stable/c/7d3b793faaab1305994ce568b59d61927235f57b |