| 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-26898: aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts |
| |
| This patch is against CVE-2023-6270. The description of cve is: |
| |
| A flaw was found in the ATA over Ethernet (AoE) driver in the Linux |
| kernel. The aoecmd_cfg_pkts() function improperly updates the refcnt on |
| `struct net_device`, and a use-after-free can be triggered by racing |
| between the free on the struct and the access through the `skbtxq` |
| global queue. This could lead to a denial of service condition or |
| potential code execution. |
| |
| In aoecmd_cfg_pkts(), it always calls dev_put(ifp) when skb initial |
| code is finished. But the net_device ifp will still be used in |
| later tx()->dev_queue_xmit() in kthread. Which means that the |
| dev_put(ifp) should NOT be called in the success path of skb |
| initial code in aoecmd_cfg_pkts(). Otherwise tx() may run into |
| use-after-free because the net_device is freed. |
| |
| This patch removed the dev_put(ifp) in the success path in |
| aoecmd_cfg_pkts(), and added dev_put() after skb xmit in tx(). |
| |
| The Linux kernel CVE team has assigned CVE-2024-26898 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 4.19.311 with commit ad80c34944d7175fa1f5c7a55066020002921a99 |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 5.4.273 with commit 1a54aa506b3b2f31496731039e49778f54eee881 |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 5.10.214 with commit faf0b4c5e00bb680e8e43ac936df24d3f48c8e65 |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 5.15.153 with commit 7dd09fa80b0765ce68bfae92f4e2f395ccf0fba4 |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 6.1.83 with commit 74ca3ef68d2f449bc848c0a814cefc487bf755fa |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 6.6.23 with commit eb48680b0255a9e8a9bdc93d6a55b11c31262e62 |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 6.7.11 with commit 079cba4f4e307c69878226fdf5228c20aa1c969c |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 6.8.2 with commit a16fbb80064634b254520a46395e36b87ca4731e |
| Issue introduced in 2.6.22 with commit 7562f876cd93800f2f8c89445f2a563590b24e09 and fixed in 6.9 with commit f98364e926626c678fb4b9004b75cacf92ff0662 |
| |
| 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-26898 |
| 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/block/aoe/aoecmd.c |
| drivers/block/aoe/aoenet.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/ad80c34944d7175fa1f5c7a55066020002921a99 |
| https://git.kernel.org/stable/c/1a54aa506b3b2f31496731039e49778f54eee881 |
| https://git.kernel.org/stable/c/faf0b4c5e00bb680e8e43ac936df24d3f48c8e65 |
| https://git.kernel.org/stable/c/7dd09fa80b0765ce68bfae92f4e2f395ccf0fba4 |
| https://git.kernel.org/stable/c/74ca3ef68d2f449bc848c0a814cefc487bf755fa |
| https://git.kernel.org/stable/c/eb48680b0255a9e8a9bdc93d6a55b11c31262e62 |
| https://git.kernel.org/stable/c/079cba4f4e307c69878226fdf5228c20aa1c969c |
| https://git.kernel.org/stable/c/a16fbb80064634b254520a46395e36b87ca4731e |
| https://git.kernel.org/stable/c/f98364e926626c678fb4b9004b75cacf92ff0662 |