[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091714-CVE-2022-50358-6a86@gregkh>
Date: Wed, 17 Sep 2025 16:56:17 +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-50358: brcmfmac: return error when getting invalid max_flowrings from dongle
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
brcmfmac: return error when getting invalid max_flowrings from dongle
When firmware hit trap at initialization, host will read abnormal
max_flowrings number from dongle, and it will cause kernel panic when
doing iowrite to initialize dongle ring.
To detect this error at early stage, we directly return error when getting
invalid max_flowrings(>256).
The Linux kernel CVE team has assigned CVE-2022-50358 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.229 with commit 3cc9299036bdb647408e11e41de3eb1ff6d428cd
Fixed in 5.10.163 with commit 2e8bb402b060a6c22160de3d72cee057698177c8
Fixed in 5.15.86 with commit 10c4b63d09a5b0ebf1b61af1dae7f25555cf58b6
Fixed in 6.0.16 with commit 87f126b25fa8562196f0f4c0aa46a446026199bf
Fixed in 6.1.2 with commit 200347eb3b2608cc8b54c13dd1d5e03809ba2eb2
Fixed in 6.2 with commit 2aca4f3734bd717e04943ddf340d49ab62299a00
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-50358
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/pcie.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/3cc9299036bdb647408e11e41de3eb1ff6d428cd
https://git.kernel.org/stable/c/2e8bb402b060a6c22160de3d72cee057698177c8
https://git.kernel.org/stable/c/10c4b63d09a5b0ebf1b61af1dae7f25555cf58b6
https://git.kernel.org/stable/c/87f126b25fa8562196f0f4c0aa46a446026199bf
https://git.kernel.org/stable/c/200347eb3b2608cc8b54c13dd1d5e03809ba2eb2
https://git.kernel.org/stable/c/2aca4f3734bd717e04943ddf340d49ab62299a00
Powered by blists - more mailing lists