CVE-2022-50358

brcmfmac: return error when getting invalid max_flowrings from dongle

MEDIUM
4.2
CVSS Score
Published: September 17, 2025 at 02:56 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
Severity
MEDIUM4.2
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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).

Affected

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

v < 5.4.2293.17 ≤ v < 5.10.1633.17 ≤ v < 5.15.863.17 ≤ v < 5.4.2293.17 ≤ v < 6.0.163.17 ≤ v < 6.1.23.17 ≤ v < 6.25.11 ≤ v < 5.15.865.16 ≤ v < 6.0.165.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.23.179e37f045d5e7f33450515f237c2f6f6bfee137dd
Vendor states this is fixed in 10c4b63d09a5b0ebf1b61af1dae7f25555cf58b6 (fixed)
Vendor states this is fixed in 200347eb3b2608cc8b54c13dd1d5e03809ba2eb2 (fixed)
Vendor states this is fixed in 2aca4f3734bd717e04943ddf340d49ab62299a00 (fixed)
Vendor states this is fixed in 2e8bb402b060a6c22160de3d72cee057698177c8 (fixed)
Vendor states this is fixed in 3cc9299036bdb647408e11e41de3eb1ff6d428cd (fixed)
Vendor states this is fixed in 87f126b25fa8562196f0f4c0aa46a446026199bf (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.2MEDIUMCISA-ADP
Attack Vector
PHYSICAL
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card