CVE-2022-50551

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-10-07. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-32015 (ENISA EUVD) · GHSA-3cj2-mw4r-3p6w (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request()

This patch fixes a shift-out-of-bounds in brcmfmac that occurs in BIT(chiprev) when a 'chiprev' provided by the device is too large. It should also not be equal to or greater than BITS_PER_TYPE(u32) as we do bitwise AND with a u32 variable and BIT(chiprev). The patch adds a check that makes the function return NULL if that is the case. Note that the NULL case is later handled by the bus-specific caller, brcmf_usb_probe_cb() or brcmf_usb_reset_resume(), for example.

Found by a modified version of syzkaller.

UBSAN: shift-out-of-bounds in drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c shift exponent 151055786 is too large for 64-bit type 'long unsigned int' CPU: 0 PID: 1885 Comm: kworker/0:2 Tainted: G O 5.14.0+ #132 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 Workqueue: usb_hub_wq hub_event Call Trace: dump_stack_lvl+0x57/0x7d ubsan_epilogue+0x5/0x40 __ubsan_handle_shift_out_of_bounds.cold+0x53/0xdb ? lock_chain_count+0x20/0x20 brcmf_fw_alloc_request.cold+0x19/0x3ea ? brcmf_fw_get_firmwares+0x250/0x250 ? brcmf_usb_ioctl_resp_wait+0x1a7/0x1f0 brcmf_usb_get_fwname+0x114/0x1a0 ? brcmf_usb_reset_resume+0x120/0x120 ? number+0x6c4/0x9a0 brcmf_c_process_clm_blob+0x168/0x590 ? put_dec+0x90/0x90 ? enable_ptr_key_workfn+0x20/0x20 ? brcmf_common_pd_remove+0x50/0x50 ? rcu_read_lock_sched_held+0xa1/0xd0 brcmf_c_preinit_dcmds+0x673/0xc40 ? brcmf_c_set_joinpref_default+0x100/0x100 ? rcu_read_lock_sched_held+0xa1/0xd0 ? rcu_read_lock_bh_held+0xb0/0xb0 ? lock_acquire+0x19d/0x4e0 ? find_held_lock+0x2d/0x110 ? brcmf_usb_deq+0x1cc/0x260 ? mark_held_locks+0x9f/0xe0 ? lockdep_hardirqs_on_prepare+0x273/0x3e0 ? _raw_spin_unlock_irqrestore+0x47/0x50 ? trace_hardirqs_on+0x1c/0x120 ? brcmf_usb_deq+0x1a7/0x260 ? brcmf_usb_rx_fill_all+0x5a/0xf0 brcmf_attach+0x246/0xd40 ? wiphy_new_nm+0x1476/0x1d50 ? kmemdup+0x30/0x40 brcmf_usb_probe+0x12de/0x1690 ? brcmf_usbdev_qinit.constprop.0+0x470/0x470 usb_probe_interface+0x25f/0x710 really_probe+0x1be/0xa90 __driver_probe_device+0x2ab/0x460 ? usb_match_id.part.0+0x88/0xc0 driver_probe_device+0x49/0x120 __device_attach_driver+0x18a/0x250 ? driver_allows_async_probing+0x120/0x120 bus_for_each_drv+0x123/0x1a0 ? bus_rescan_devices+0x20/0x20 ? lockdep_hardirqs_on_prepare+0x273/0x3e0 ? trace_hardirqs_on+0x1c/0x120 __device_attach+0x207/0x330 ? device_bind_driver+0xb0/0xb0 ? kobject_uevent_env+0x230/0x12c0 bus_probe_device+0x1a2/0x260 device_add+0xa61/0x1ce0 ? __mutex_unlock_slowpath+0xe7/0x660 ? __fw_devlink_link_to_suppliers+0x550/0x550 usb_set_configuration+0x984/0x1770 ? kernfs_create_link+0x175/0x230 usb_generic_driver_probe+0x69/0x90 usb_probe_device+0x9c/0x220 really_probe+0x1be/0xa90 __driver_probe_device+0x2ab/0x460 driver_probe_device+0x49/0x120 __device_attach_driver+0x18a/0x250 ? driver_allows_async_probing+0x120/0x120 bus_for_each_drv+0x123/0x1a0 ? bus_rescan_devices+0x20/0x20 ? lockdep_hardirqs_on_prepare+0x273/0x3e0 ? trace_hardirqs_on+0x1c/0x120 __device_attach+0x207/0x330 ? device_bind_driver+0xb0/0xb0 ? kobject_uevent_env+0x230/0x12c0 bus_probe_device+0x1a2/0x260 device_add+0xa61/0x1ce0 ? __fw_devlink_link_to_suppliers+0x550/0x550 usb_new_device.cold+0x463/0xf66 ? hub_disconnect+0x400/0x400 ? _raw_spin_unlock_irq+0x24/0x30 hub_event+0x10d5/0x3330 ? hub_port_debounce+0x280/0x280 ? __lock_acquire+0x1671/0x5790 ? wq_calc_node_cpumask+0x170/0x2a0 ? lock_release+0x640/0x640 ? rcu_read_lock_sched_held+0xa1/0xd0 ? rcu_read_lock_bh_held+0xb0/0xb0 ? lockdep_hardirqs_on_prepare+0x273/0x3e0 process_one_work+0x873/0x13e0 ? lock_release+0x640/0x640 ? pwq_dec_nr_in_flight+0x320/0x320 ? rwlock_bug.part.0+0x90/0x90 worker_thread+0x8b/0xd10 ? __kthread_parkme+0xd9/0x1d0 ? pr ---truncated---

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2025

Last Modified

November 5, 2026

Advisory Details (10)

Auto-updated Nov 12, 2026
Patch available.
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ffb589963df103caaf062081a32db0b9e1798660
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bc45aa1911bf699b9905f12414e3c1879d6b784f
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d2f70fa2c7cc6c73a420ff15682454782d3d6f6
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87792567d9ed93fd336d2c3b8d7870f44e141e6d
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81d17f6f3331f03c8eafdacea68ab773426c1e3c
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b06a8a25eba07628313aa3c5496522eff97be53
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/579c9b9838e8a73f6e93ddece07972c241514dcc
Web page

wifi: brcmfmac: fix up incorrect 4.14.y backport for brcmf_fw_map_chip_to_name() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c8fc44c44b97854623c56363c359f711fc0b887
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1db036d13e10809943c2dce553e2fa7fc9c6cd80
Web page

wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b12d2aa264bac35bff9b5399bb162262b2b8949

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.337 (fixes >=4.5.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 210 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-14 17:26 UTCOSV refresh
  2. 2026-11-13 16:43 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-11-12 11:25 UTCEchelonGraph re-scored
  5. 2026-11-12 11:25 UTCGHSA enrichmentGHSA-3cj2-mw4r-3p6w · GitHub severity HIGH · GitHub CVSS 7.1
  6. 2026-11-11 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-11-10 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-11-08 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-11-07 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-11-05 21:27 UTCGHSA enrichmentGHSA-3cj2-mw4r-3p6w · GitHub severity HIGH · GitHub CVSS 7.1
  13. 2026-11-05 20:27 UTCEchelonGraph re-scored
  14. 2026-11-05 20:27 UTCGHSA enrichmentGHSA-3cj2-mw4r-3p6w · GitHub severity HIGH · GitHub CVSS 7.1
  15. 2026-11-05 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-11-03 20:57 UTCEchelonGraph re-scored
  18. 2026-11-03 20:57 UTCGHSA enrichmentGHSA-3cj2-mw4r-3p6w · GitHub severity HIGH · GitHub CVSS 7.1
  19. 2026-11-03 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 75 more
  1. 2026-10-28 05:17 UTCEchelonGraph re-scored
  2. 2026-10-28 05:17 UTCGHSA enrichmentGHSA-3cj2-mw4r-3p6w · GitHub severity HIGH · GitHub CVSS 7.1
  3. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-25 17:53 UTCEchelonGraph re-scored
  6. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-21 05:29 UTCEchelonGraph re-scored
  12. 2026-10-21 05:29 UTCGHSA enrichmentGHSA-3cj2-mw4r-3p6w · GitHub severity HIGH · GitHub CVSS 7.1
  13. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-18 08:18 UTCEchelonGraph re-scored
  17. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-12 18:40 UTCEchelonGraph re-scored
  23. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-11 22:04 UTCEchelonGraph re-scored
  25. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  26. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-10-02 03:11 UTCOSV refresh
  35. 2026-09-30 16:13 UTCEchelonGraph re-scored
  36. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  40. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  42. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  44. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  46. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  47. 2026-09-12 21:06 UTCOSV refresh
  48. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  49. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  50. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  52. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  59. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  62. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  63. 2026-08-25 01:56 UTCOSV refresh
  64. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  65. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  66. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  67. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  68. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  69. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  70. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  71. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  72. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  73. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  74. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  75. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-50551?
CVE-2022-50551 is a high-severity vulnerability; its CVE record was published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() This patch fixes a shift-out-of-bounds in brcmfmac that occurs in BIT(chiprev) when a 'chiprev' provided by the device is too large. It should also not…
When was the CVE record for CVE-2022-50551 published?
The CVE record for CVE-2022-50551 was published on October 7, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2022-50551 actively exploited?
CVE-2022-50551 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50551?
CVE-2022-50551 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2022-50551?
A fix for CVE-2022-50551 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50551

Explore →

Is Your Infrastructure Affected by CVE-2022-50551?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs