CVE-2023-53213

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-09-15. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2023-59871 (ENISA EUVD) · GHSA-fq2q-2mv8-c2mg (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: slab-out-of-bounds read in brcmf_get_assoc_ies()

Fix a slab-out-of-bounds read that occurs in kmemdup() called from brcmf_get_assoc_ies(). The bug could occur when assoc_info->req_len, data from a URB provided by a USB device, is bigger than the size of buffer which is defined as WL_EXTRA_BUF_MAX.

Add the size check for req_len/resp_len of assoc_info.

Found by a modified version of syzkaller.

[ 46.592467][ T7] ================================================================== [ 46.594687][ T7] BUG: KASAN: slab-out-of-bounds in kmemdup+0x3e/0x50 [ 46.596572][ T7] Read of size 3014656 at addr ffff888019442000 by task kworker/0:1/7 [ 46.598575][ T7] [ 46.599157][ T7] CPU: 0 PID: 7 Comm: kworker/0:1 Tainted: G O 5.14.0+ #145 [ 46.601333][ T7] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 [ 46.604360][ T7] Workqueue: events brcmf_fweh_event_worker [ 46.605943][ T7] Call Trace: [ 46.606584][ T7] dump_stack_lvl+0x8e/0xd1 [ 46.607446][ T7] print_address_description.constprop.0.cold+0x93/0x334 [ 46.608610][ T7] ? kmemdup+0x3e/0x50 [ 46.609341][ T7] kasan_report.cold+0x79/0xd5 [ 46.610151][ T7] ? kmemdup+0x3e/0x50 [ 46.610796][ T7] kasan_check_range+0x14e/0x1b0 [ 46.611691][ T7] memcpy+0x20/0x60 [ 46.612323][ T7] kmemdup+0x3e/0x50 [ 46.612987][ T7] brcmf_get_assoc_ies+0x967/0xf60 [ 46.613904][ T7] ? brcmf_notify_vif_event+0x3d0/0x3d0 [ 46.614831][ T7] ? lock_chain_count+0x20/0x20 [ 46.615683][ T7] ? mark_lock.part.0+0xfc/0x2770 [ 46.616552][ T7] ? lock_chain_count+0x20/0x20 [ 46.617409][ T7] ? mark_lock.part.0+0xfc/0x2770 [ 46.618244][ T7] ? lock_chain_count+0x20/0x20 [ 46.619024][ T7] brcmf_bss_connect_done.constprop.0+0x241/0x2e0 [ 46.620019][ T7] ? brcmf_parse_configure_security.isra.0+0x2a0/0x2a0 [ 46.620818][ T7] ? __lock_acquire+0x181f/0x5790 [ 46.621462][ T7] brcmf_notify_connect_status+0x448/0x1950 [ 46.622134][ T7] ? rcu_read_lock_bh_held+0xb0/0xb0 [ 46.622736][ T7] ? brcmf_cfg80211_join_ibss+0x7b0/0x7b0 [ 46.623390][ T7] ? find_held_lock+0x2d/0x110 [ 46.623962][ T7] ? brcmf_fweh_event_worker+0x19f/0xc60 [ 46.624603][ T7] ? mark_held_locks+0x9f/0xe0 [ 46.625145][ T7] ? lockdep_hardirqs_on_prepare+0x3e0/0x3e0 [ 46.625871][ T7] ? brcmf_cfg80211_join_ibss+0x7b0/0x7b0 [ 46.626545][ T7] brcmf_fweh_call_event_handler.isra.0+0x90/0x100 [ 46.627338][ T7] brcmf_fweh_event_worker+0x557/0xc60 [ 46.627962][ T7] ? brcmf_fweh_call_event_handler.isra.0+0x100/0x100 [ 46.628736][ T7] ? rcu_read_lock_sched_held+0xa1/0xd0 [ 46.629396][ T7] ? rcu_read_lock_bh_held+0xb0/0xb0 [ 46.629970][ T7] ? lockdep_hardirqs_on_prepare+0x273/0x3e0 [ 46.630649][ T7] process_one_work+0x92b/0x1460 [ 46.631205][ T7] ? pwq_dec_nr_in_flight+0x330/0x330 [ 46.631821][ T7] ? rwlock_bug.part.0+0x90/0x90 [ 46.632347][ T7] worker_thread+0x95/0xe00 [ 46.632832][ T7] ? __kthread_parkme+0x115/0x1e0 [ 46.633393][ T7] ? process_one_work+0x1460/0x1460 [ 46.633957][ T7] kthread+0x3a1/0x480 [ 46.634369][ T7] ? set_kthread_struct+0x120/0x120 [ 46.634933][ T7] ret_from_fork+0x1f/0x30 [ 46.635431][ T7] [ 46.635687][ T7] Allocated by task 7: [ 46.636151][ T7] kasan_save_stack+0x1b/0x40 [ 46.636628][ T7] __kasan_kmalloc+0x7c/0x90 [ 46.637108][ T7] kmem_cache_alloc_trace+0x19e/0x330 [ 46.637696][ T7] brcmf_cfg80211_attach+0x4a0/0x4040 [ 46.638275][ T7] brcmf_attach+0x389/0xd40 [ 46.638739][ T7] brcmf_usb_probe+0x12de/0x1690 [ 46.639279][ T7] usb_probe_interface+0x2aa/0x760 [ 46.639820][ T7] really_probe+0x205/0xb70 [ 46.640342][ T7] __driver_probe_device+0 ---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
15th
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-10-27). 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

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
Patch available.
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0da40e018fd034d87c9460123fa7f897b69fdee7
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21bee3e649d87f78fe8aef6ae02edd3d6f310fd0
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/228186629ea970cc78b7d7d5f593f2d32fddf9f6
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/936a23293bbb3332bdf4cdb9c1496e80cb0bc2c8
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/549825602e3e6449927ca1ea1a08fd89868439df
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/425eea395f1f5ae349fb55f7fe51d833a5324bfe
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39f9bd880abac6068bedb24a4e16e7bd26bf92da
Web page

wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac5305e5d227b9af3aae25fa83380d3ff0225b73

Vendor Advisories for CVE-2023-53213(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-193.178.1.el8_22025-12-17redhat
redhatkernel-0:4.18.0-305.179.1.el8_42025-12-04redhat
redhatkernel-rt-0:5.14.0-70.153.1.rt21.225.el9_02025-11-12redhat
redhatkernel-0:5.14.0-284.146.1.el9_22025-11-12redhat
redhatkernel-0:4.18.0-477.118.1.el8_82025-11-12redhat
redhatkernel-0:4.18.0-372.168.1.el8_62025-11-12redhat
redhatkernel-0:5.14.0-70.153.1.el9_02025-11-12redhat
redhatkernel-rt-0:5.14.0-284.146.1.rt14.431.el9_22025-11-12redhat
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.14.315 (fixes >=2.6.37)—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 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.27-1: fixed in 6.1.27-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.27-1: fixed in 6.1.27-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.27-1: fixed in 6.1.27-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 94 of 205 refreshes 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53213?
CVE-2023-53213 is a high-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() Fix a slab-out-of-bounds read that occurs in kmemdup() called from brcmf_get_assoc_ies(). The bug could occur when assoc_info->req_len, data from a URB provided by a…
When was the CVE record for CVE-2023-53213 published?
The CVE record for CVE-2023-53213 was published on September 15, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53213 actively exploited?
CVE-2023-53213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53213?
CVE-2023-53213 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2023-53213?
A fix for CVE-2023-53213 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53213 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53213

Explore →

Is Your Infrastructure Affected by CVE-2023-53213?

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

Book a Demo →Browse All CVEs