| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025022752-CVE-2025-21802-0cc5@gregkh> Date: Thu, 27 Feb 2025 11:59:56 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2025-21802: net: hns3: fix oops when unload drivers paralleling Description =========== In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix oops when unload drivers paralleling When unload hclge driver, it tries to disable sriov first for each ae_dev node from hnae3_ae_dev_list. If user unloads hns3 driver at the time, because it removes all the ae_dev nodes, and it may cause oops. But we can't simply use hnae3_common_lock for this. Because in the process flow of pci_disable_sriov(), it will trigger the remove flow of VF, which will also take hnae3_common_lock. To fixes it, introduce a new mutex to protect the unload process. The Linux kernel CVE team has assigned CVE-2025-21802 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 0dd8a25f355b4df2d41c08df1716340854c7d4c5 and fixed in 6.1.129 with commit e876522659012ef2e73834a0b9f1cbe3f74d5fad Issue introduced in 5.15 with commit 0dd8a25f355b4df2d41c08df1716340854c7d4c5 and fixed in 6.6.76 with commit b5a8bc47aa0a4aa8bca5466dfa2d12dbb5b3cd0c Issue introduced in 5.15 with commit 0dd8a25f355b4df2d41c08df1716340854c7d4c5 and fixed in 6.12.13 with commit 82736bb83fb0221319c85c2e9917d0189cd84e1e Issue introduced in 5.15 with commit 0dd8a25f355b4df2d41c08df1716340854c7d4c5 and fixed in 6.13.2 with commit cafe9a27e22736d4a01b3933e36225f9857c7988 Issue introduced in 5.15 with commit 0dd8a25f355b4df2d41c08df1716340854c7d4c5 and fixed in 6.14-rc1 with commit 92e5995773774a3e70257e9c95ea03518268bea5 Issue introduced in 4.19.214 with commit b06ad258e01389ca3ff13bc180f3fcd6a608f1cd Issue introduced in 5.4.156 with commit c4b64011e458aa2b246cd4e42012cfd83d2d9a5c Issue introduced in 5.10.76 with commit d36b15e3e7b5937cb1f6ac590a85facc3a320642 Issue introduced in 5.14.15 with commit 9b5a29f0acefa3eb1dbe2fa302b393eeff64d933 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-2025-21802 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/net/ethernet/hisilicon/hns3/hnae3.c drivers/net/ethernet/hisilicon/hns3/hnae3.h drivers/net/ethernet/hisilicon/hns3/hns3_enet.c drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.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/e876522659012ef2e73834a0b9f1cbe3f74d5fad https://git.kernel.org/stable/c/b5a8bc47aa0a4aa8bca5466dfa2d12dbb5b3cd0c https://git.kernel.org/stable/c/82736bb83fb0221319c85c2e9917d0189cd84e1e https://git.kernel.org/stable/c/cafe9a27e22736d4a01b3933e36225f9857c7988 https://git.kernel.org/stable/c/92e5995773774a3e70257e9c95ea03518268bea5
Powered by blists - more mailing lists