| 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: <2025091553-CVE-2022-50321-bba8@gregkh> Date: Mon, 15 Sep 2025 16:48:58 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50321: wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit() The brcmf_netdev_start_xmit() returns NETDEV_TX_OK without freeing skb in case of pskb_expand_head() fails, add dev_kfree_skb() to fix it. Compile tested only. The Linux kernel CVE team has assigned CVE-2022-50321 to this issue. Affected and fixed versions =========================== Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 4.14.308 with commit 4c55fdebc1c358de96bfab52ed309d58a3ba66ef Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 4.19.276 with commit e5d01e85cf46628647cd696cb72ba4659b18967f Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 5.4.235 with commit d869a189505224601e310c7769cb90b0e2f60b31 Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 5.10.173 with commit e08e6812efb6a8c676e733de0518594d1517e0d9 Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 5.15.99 with commit e8ef89e5b89ee041a94eecfb6c31fcc237f9168c Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 6.1.16 with commit 7f159116d620615779adbf88a5d94713702216d8 Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 6.2.3 with commit 3a4d18318f473e97d628f410215b3fac32d07aed Issue introduced in 4.13 with commit 270a6c1f65fe68a28a5d39cd405592c550b496c7 and fixed in 6.3 with commit 212fde3fe76e962598ce1d47b97cc78afdfc71b3 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-50321 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/wireless/broadcom/brcm80211/brcmfmac/core.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/4c55fdebc1c358de96bfab52ed309d58a3ba66ef https://git.kernel.org/stable/c/e5d01e85cf46628647cd696cb72ba4659b18967f https://git.kernel.org/stable/c/d869a189505224601e310c7769cb90b0e2f60b31 https://git.kernel.org/stable/c/e08e6812efb6a8c676e733de0518594d1517e0d9 https://git.kernel.org/stable/c/e8ef89e5b89ee041a94eecfb6c31fcc237f9168c https://git.kernel.org/stable/c/7f159116d620615779adbf88a5d94713702216d8 https://git.kernel.org/stable/c/3a4d18318f473e97d628f410215b3fac32d07aed https://git.kernel.org/stable/c/212fde3fe76e962598ce1d47b97cc78afdfc71b3
Powered by blists - more mailing lists