| 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-50109: md/raid10: fix null ptr dereference in raid10_size() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| md/raid10: fix null ptr dereference in raid10_size() |
| |
| In raid10_run() if raid10_set_queue_limits() succeed, the return value |
| is set to zero, and if following procedures failed raid10_run() will |
| return zero while mddev->private is still NULL, causing null ptr |
| dereference in raid10_size(). |
| |
| Fix the problem by only overwrite the return value if |
| raid10_set_queue_limits() failed. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50109 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.9 with commit 3d8466ba68d444f5528dcbff106e8bf5c7d51aa0 and fixed in 6.11.6 with commit b3054db2fd2d35f2eb3b4b5fb1407792f465391c |
| Issue introduced in 6.9 with commit 3d8466ba68d444f5528dcbff106e8bf5c7d51aa0 and fixed in 6.12 with commit 825711e00117fc686ab89ac36a9a7b252dc349c6 |
| |
| 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-50109 |
| 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: |
| drivers/md/raid10.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/b3054db2fd2d35f2eb3b4b5fb1407792f465391c |
| https://git.kernel.org/stable/c/825711e00117fc686ab89ac36a9a7b252dc349c6 |
