| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-49860: dmaengine: ti: k3-udma-glue: fix memory leak when register device fail |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| dmaengine: ti: k3-udma-glue: fix memory leak when register device fail |
| |
| If device_register() fails, it should call put_device() to give |
| up reference, the name allocated in dev_set_name() can be freed |
| in callback function kobject_cleanup(). |
| |
| The Linux kernel CVE team has assigned CVE-2022-49860 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.11 with commit 5b65781d06ea90ef2f8e51a13352c43c3daa8cdc and fixed in 5.15.79 with commit 1dd27541aa2b95bde71bddd43d73f9c16d73272c |
| Issue introduced in 5.11 with commit 5b65781d06ea90ef2f8e51a13352c43c3daa8cdc and fixed in 6.0.9 with commit 025eab5189fc7ee223ae9b4bc49d7df196543e53 |
| Issue introduced in 5.11 with commit 5b65781d06ea90ef2f8e51a13352c43c3daa8cdc and fixed in 6.1 with commit ac2b9f34f02052709aea7b34bb2a165e1853eb41 |
| |
| 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-2022-49860 |
| 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/dma/ti/k3-udma-glue.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/1dd27541aa2b95bde71bddd43d73f9c16d73272c |
| https://git.kernel.org/stable/c/025eab5189fc7ee223ae9b4bc49d7df196543e53 |
| https://git.kernel.org/stable/c/ac2b9f34f02052709aea7b34bb2a165e1853eb41 |
