| 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-53180: ALSA: pcm: Add sanity NULL check for the default mmap fault handler |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ALSA: pcm: Add sanity NULL check for the default mmap fault handler |
| |
| A driver might allow the mmap access before initializing its |
| runtime->dma_area properly. Add a proper NULL check before passing to |
| virt_to_page() for avoiding a panic. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53180 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.15.174 with commit 8799f4332a9fd812eadfbc32fc5104d6292f754f |
| Fixed in 6.1.120 with commit 832efbb74b1578e3737d593a204d42af8bd1b81b |
| Fixed in 6.6.64 with commit bc200027ee92fba84f1826494735ed675f3aa911 |
| Fixed in 6.11.11 with commit f0ce9e24eff1678c16276f9717f26a78202506a2 |
| Fixed in 6.12.2 with commit 0c4c9bf5eab7bee6b606f2abb0993e933b5831a0 |
| Fixed in 6.13 with commit d2913a07d9037fe7aed4b7e680684163eaed6bc4 |
| |
| 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-53180 |
| 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: |
| sound/core/pcm_native.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/8799f4332a9fd812eadfbc32fc5104d6292f754f |
| https://git.kernel.org/stable/c/832efbb74b1578e3737d593a204d42af8bd1b81b |
| https://git.kernel.org/stable/c/bc200027ee92fba84f1826494735ed675f3aa911 |
| https://git.kernel.org/stable/c/f0ce9e24eff1678c16276f9717f26a78202506a2 |
| https://git.kernel.org/stable/c/0c4c9bf5eab7bee6b606f2abb0993e933b5831a0 |
| https://git.kernel.org/stable/c/d2913a07d9037fe7aed4b7e680684163eaed6bc4 |
