CVE-2022-50551

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

October 7, 2025

Last Modified

February 26, 2026

References (10)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.337—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 105 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-50551?
CVE-2022-50551 is a high vulnerability published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmffwalloc_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…
When was CVE-2022-50551 disclosed?
CVE-2022-50551 was first published in the National Vulnerability Database on October 7, 2025, with the most recent update on February 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50551 actively exploited?
CVE-2022-50551 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50551, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs