| 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-56730: net/9p/usbg: fix handling of the failed kzalloc() memory allocation |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net/9p/usbg: fix handling of the failed kzalloc() memory allocation |
| |
| On the linux-next, next-20241108 vanilla kernel, the coccinelle tool gave the |
| following error report: |
| |
| ./net/9p/trans_usbg.c:912:5-11: ERROR: allocation function on line 911 returns |
| NULL not ERR_PTR on failure |
| |
| kzalloc() failure is fixed to handle the NULL return case on the memory exhaustion. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56730 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.12.2 with commit 2cdb416de8b5795fd25fadcb69e1198b6df6d8cc |
| Issue introduced in 6.12 with commit a3be076dc174d9022a71a12554feb4c97b5c4d5c and fixed in 6.13 with commit ff1060813d9347e8c45c8b8cff93a4dfdb6726ad |
| |
| 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-56730 |
| 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: |
| net/9p/trans_usbg.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/2cdb416de8b5795fd25fadcb69e1198b6df6d8cc |
| https://git.kernel.org/stable/c/ff1060813d9347e8c45c8b8cff93a4dfdb6726ad |
