| 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-56595: jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree |
| |
| When the value of lp is 0 at the beginning of the for loop, it will |
| become negative in the next assignment and we should bail out. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56595 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.4.287 with commit b15000bcbecf27e0f7c0f149a409e5b865e28ca2 |
| Fixed in 5.10.231 with commit 368a533152220b0a6f1142327d96c6b6361f3002 |
| Fixed in 5.15.174 with commit a3d408870bc19b794646871bc4c3a5daa66f91c5 |
| Fixed in 6.1.120 with commit 491487eeddccc4bb49f2e59d8c8f35bec89c15ca |
| Fixed in 6.6.66 with commit 3b5d21b56c3774bc84eab0a93aaac22a4475e2c4 |
| Fixed in 6.12.5 with commit 8a4311bbde702362fe7412045d06ab6767235dac |
| Fixed in 6.13 with commit a174706ba4dad895c40b1d2277bade16dfacdcd9 |
| |
| 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-56595 |
| 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: |
| fs/jfs/jfs_dmap.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/b15000bcbecf27e0f7c0f149a409e5b865e28ca2 |
| https://git.kernel.org/stable/c/368a533152220b0a6f1142327d96c6b6361f3002 |
| https://git.kernel.org/stable/c/a3d408870bc19b794646871bc4c3a5daa66f91c5 |
| https://git.kernel.org/stable/c/491487eeddccc4bb49f2e59d8c8f35bec89c15ca |
| https://git.kernel.org/stable/c/3b5d21b56c3774bc84eab0a93aaac22a4475e2c4 |
| https://git.kernel.org/stable/c/8a4311bbde702362fe7412045d06ab6767235dac |
| https://git.kernel.org/stable/c/a174706ba4dad895c40b1d2277bade16dfacdcd9 |
