CVE-2022-50321

wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit()

MEDIUM

5.5

CVSS Score

Published: September 15, 2025 at 02:48 PM UTC

Updated: June 17, 2026 at 05:23 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.13 ≤ v < 4.14.3084.13 ≤ v < 4.19.2764.13 ≤ v < 5.10.1734.13 ≤ v < 5.15.994.13 ≤ v < 5.4.2354.13 ≤ v < 6.1.164.13 ≤ v < 6.2.34.13 ≤ v < 6.34.15 ≤ v < 4.19.2764.20 ≤ v < 5.4.2355.11 ≤ v < 5.15.995.16 ≤ v < 6.1.165.5 ≤ v < 5.10.1736.2 ≤ v < 6.2.3270a6c1f65fe68a28a5d39cd405592c550b496c74.13

Vendor states this is fixed in 212fde3fe76e962598ce1d47b97cc78afdfc71b3 (fixed)

Vendor states this is fixed in 3a4d18318f473e97d628f410215b3fac32d07aed (fixed)

Vendor states this is fixed in 4c55fdebc1c358de96bfab52ed309d58a3ba66ef (fixed)

Vendor states this is fixed in 7f159116d620615779adbf88a5d94713702216d8 (fixed)

Vendor states this is fixed in d869a189505224601e310c7769cb90b0e2f60b31 (fixed)

Vendor states this is fixed in e08e6812efb6a8c676e733de0518594d1517e0d9 (fixed)

Vendor states this is fixed in e5d01e85cf46628647cd696cb72ba4659b18967f (fixed)

Vendor states this is fixed in e8ef89e5b89ee041a94eecfb6c31fcc237f9168c (fixed)

Vendor states this is fixed in 4.13 (unaffected)

Vendor states this is fixed in 4.14.308 (unaffected)

Vendor states this is fixed in 4.19.276 (unaffected)

Vendor states this is fixed in 5.10.173 (unaffected)