| 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-50205: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() |
| |
| The step variable is initialized to zero. It is changed in the loop, |
| but if it's not changed it will remain zero. Add a variable check |
| before the division. |
| |
| The observed behavior was introduced by commit 826b5de90c0b |
| ("ALSA: firewire-lib: fix insufficient PCM rule for period/buffer size"), |
| and it is difficult to show that any of the interval parameters will |
| satisfy the snd_interval_test() condition with data from the |
| amdtp_rate_table[] table. |
| |
| Found by Linux Verification Center (linuxtesting.org) with SVACE. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50205 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 5.4.285 with commit d575414361630b8b0523912532fcd7c79e43468c |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 5.10.229 with commit 5e431f85c87bbffd93a9830d5a576586f9855291 |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 5.15.170 with commit 7d4eb9e22131ec154e638cbd56629195c9bcbe9a |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 6.1.115 with commit d2826873db70a6719cdd9212a6739f3e6234cfc4 |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 6.6.59 with commit 4bdc21506f12b2d432b1f2667e5ff4c75eee58e3 |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 6.11.6 with commit 3452d39c4704aa12504e4190298c721fb01083c3 |
| Issue introduced in 4.20 with commit 826b5de90c0bca4e9de6231da9e1730480621588 and fixed in 6.12 with commit 72cafe63b35d06b5cfbaf807e90ae657907858da |
| |
| 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-50205 |
| 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/firewire/amdtp-stream.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/d575414361630b8b0523912532fcd7c79e43468c |
| https://git.kernel.org/stable/c/5e431f85c87bbffd93a9830d5a576586f9855291 |
| https://git.kernel.org/stable/c/7d4eb9e22131ec154e638cbd56629195c9bcbe9a |
| https://git.kernel.org/stable/c/d2826873db70a6719cdd9212a6739f3e6234cfc4 |
| https://git.kernel.org/stable/c/4bdc21506f12b2d432b1f2667e5ff4c75eee58e3 |
| https://git.kernel.org/stable/c/3452d39c4704aa12504e4190298c721fb01083c3 |
| https://git.kernel.org/stable/c/72cafe63b35d06b5cfbaf807e90ae657907858da |
