| 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-56596: jfs: fix array-index-out-of-bounds in jfs_readdir |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| jfs: fix array-index-out-of-bounds in jfs_readdir |
| |
| The stbl might contain some invalid values. Added a check to |
| return error code in that case. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56596 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.4.287 with commit b62f41aeec9d250144c53875b507c1d45ae8c8fc |
| Fixed in 5.10.231 with commit 97e693593162eef6851d232f0c8148169ed46a5c |
| Fixed in 5.15.174 with commit 9efe72eefd4c4a7ce63b3e4d667d766d2b360cb4 |
| Fixed in 6.1.120 with commit ff9fc48fab0e1ea0d423c23c99b91bba178f0b05 |
| Fixed in 6.6.66 with commit e7d376f94f72b020f84e77278b150ec1cc27502c |
| Fixed in 6.12.5 with commit 8ff7579554571d92e3deab168f5a7d7b146ed368 |
| Fixed in 6.13 with commit 839f102efb168f02dfdd46717b7c6dddb26b015e |
| |
| 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-56596 |
| 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_dtree.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/b62f41aeec9d250144c53875b507c1d45ae8c8fc |
| https://git.kernel.org/stable/c/97e693593162eef6851d232f0c8148169ed46a5c |
| https://git.kernel.org/stable/c/9efe72eefd4c4a7ce63b3e4d667d766d2b360cb4 |
| https://git.kernel.org/stable/c/ff9fc48fab0e1ea0d423c23c99b91bba178f0b05 |
| https://git.kernel.org/stable/c/e7d376f94f72b020f84e77278b150ec1cc27502c |
| https://git.kernel.org/stable/c/8ff7579554571d92e3deab168f5a7d7b146ed368 |
| https://git.kernel.org/stable/c/839f102efb168f02dfdd46717b7c6dddb26b015e |
