| 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-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() |
| |
| Fix an unwind issue in mlx5vf_add_migration_pages(). |
| |
| If a set of pages is allocated but fails to be added to the SG table, |
| they need to be freed to prevent a memory leak. |
| |
| Any pages successfully added to the SG table will be freed as part of |
| mlx5vf_free_data_buffer(). |
| |
| The Linux kernel CVE team has assigned CVE-2024-56742 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.18 with commit 6fadb021266d03c5fd7bca2cfa1607efd246dad1 and fixed in 6.11.11 with commit 769fe4ce444b646b0bf6ac308de80686c730c7df |
| Issue introduced in 5.18 with commit 6fadb021266d03c5fd7bca2cfa1607efd246dad1 and fixed in 6.12.2 with commit c44f1b2ddfa81c8d7f8e9b6bc76c427bc00e69d5 |
| Issue introduced in 5.18 with commit 6fadb021266d03c5fd7bca2cfa1607efd246dad1 and fixed in 6.13 with commit 22e87bf3f77c18f5982c19ffe2732ef0c7a25f16 |
| |
| 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-56742 |
| 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/vfio/pci/mlx5/cmd.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/769fe4ce444b646b0bf6ac308de80686c730c7df |
| https://git.kernel.org/stable/c/c44f1b2ddfa81c8d7f8e9b6bc76c427bc00e69d5 |
| https://git.kernel.org/stable/c/22e87bf3f77c18f5982c19ffe2732ef0c7a25f16 |
