| 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-50248: ntfs3: Add bounds checking to mi_enum_attr() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ntfs3: Add bounds checking to mi_enum_attr() |
| |
| Added bounds checking to make sure that every attr don't stray beyond |
| valid memory region. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50248 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.15 with commit 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e and fixed in 6.1.120 with commit 386613a44b858304a88529ade2ccc1e079a5fc56 |
| Issue introduced in 5.15 with commit 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e and fixed in 6.6.60 with commit 22cdf3be7d34f61a91b9e2966fec3a29f3871398 |
| Issue introduced in 5.15 with commit 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e and fixed in 6.11.7 with commit 809f9b419c75f8042c58434d2bfe849140643e9d |
| Issue introduced in 5.15 with commit 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e and fixed in 6.12 with commit 556bdf27c2dd5c74a9caacbe524b943a6cd42d99 |
| |
| 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-50248 |
| 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/ntfs3/record.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/386613a44b858304a88529ade2ccc1e079a5fc56 |
| https://git.kernel.org/stable/c/22cdf3be7d34f61a91b9e2966fec3a29f3871398 |
| https://git.kernel.org/stable/c/809f9b419c75f8042c58434d2bfe849140643e9d |
| https://git.kernel.org/stable/c/556bdf27c2dd5c74a9caacbe524b943a6cd42d99 |
