CVE-2022-50248

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.8; sources differ by 0.0.

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

Also known asEUVD-2022-55504 (ENISA EUVD) · GHSA-p4ww-hfqg-jmvc (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
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.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: iwlwifi: mvm: fix double free on tx path.

We see kernel crashes and lockups and KASAN errors related to ax210 firmware crashes. One of the KASAN dumps pointed at the tx path, and it appears there is indeed a way to double-free an skb.

If iwl_mvm_tx_skb_sta returns non-zero, then the 'skb' sent into the method will be freed. But, in case where we build TSO skb buffer, the skb may also be freed in error case. So, return 0 in that particular error case and do cleanup manually.

BUG: KASAN: use-after-free in __list_del_entry_valid+0x12/0x90 iwlwifi 0000:06:00.0: 0x00000000 | tsf hi Read of size 8 at addr ffff88813cfa4ba0 by task btserver/9650

CPU: 4 PID: 9650 Comm: btserver Tainted: G W 5.19.8+ #5 iwlwifi 0000:06:00.0: 0x00000000 | time gp1 Hardware name: Default string Default string/SKYBAY, BIOS 5.12 02/19/2019 Call Trace: dump_stack_lvl+0x55/0x6d print_report.cold.12+0xf2/0x684 iwlwifi 0000:06:00.0: 0x1D0915A8 | time gp2 ? __list_del_entry_valid+0x12/0x90 kasan_report+0x8b/0x180 iwlwifi 0000:06:00.0: 0x00000001 | uCode revision type ? __list_del_entry_valid+0x12/0x90 __list_del_entry_valid+0x12/0x90 iwlwifi 0000:06:00.0: 0x00000048 | uCode version major tcp_update_skb_after_send+0x5d/0x170 __tcp_transmit_skb+0xb61/0x15c0 iwlwifi 0000:06:00.0: 0xDAA05125 | uCode version minor ? __tcp_select_window+0x490/0x490 iwlwifi 0000:06:00.0: 0x00000420 | hw version ? trace_kmalloc_node+0x29/0xd0 ? __kmalloc_node_track_caller+0x12a/0x260 ? memset+0x1f/0x40 ? __build_skb_around+0x125/0x150 ? __alloc_skb+0x1d4/0x220 ? skb_zerocopy_clone+0x55/0x230 iwlwifi 0000:06:00.0: 0x00489002 | board version ? kmalloc_reserve+0x80/0x80 ? rcu_read_lock_bh_held+0x60/0xb0 tcp_write_xmit+0x3f1/0x24d0 iwlwifi 0000:06:00.0: 0x034E001C | hcmd ? __check_object_size+0x180/0x350 iwlwifi 0000:06:00.0: 0x24020000 | isr0 tcp_sendmsg_locked+0x8a9/0x1520 iwlwifi 0000:06:00.0: 0x01400000 | isr1 ? tcp_sendpage+0x50/0x50 iwlwifi 0000:06:00.0: 0x48F0000A | isr2 ? lock_release+0xb9/0x400 ? tcp_sendmsg+0x14/0x40 iwlwifi 0000:06:00.0: 0x00C3080C | isr3 ? lock_downgrade+0x390/0x390 ? do_raw_spin_lock+0x114/0x1d0 iwlwifi 0000:06:00.0: 0x00200000 | isr4 ? rwlock_bug.part.2+0x50/0x50 iwlwifi 0000:06:00.0: 0x034A001C | last cmd Id ? rwlock_bug.part.2+0x50/0x50 ? lockdep_hardirqs_on_prepare+0xe/0x200 iwlwifi 0000:06:00.0: 0x0000C2F0 | wait_event ? __local_bh_enable_ip+0x87/0xe0 ? inet_send_prepare+0x220/0x220 iwlwifi 0000:06:00.0: 0x000000C4 | l2p_control tcp_sendmsg+0x22/0x40 sock_sendmsg+0x5f/0x70 iwlwifi 0000:06:00.0: 0x00010034 | l2p_duration __sys_sendto+0x19d/0x250 iwlwifi 0000:06:00.0: 0x00000007 | l2p_mhvalid ? __ia32_sys_getpeername+0x40/0x40 iwlwifi 0000:06:00.0: 0x00000000 | l2p_addr_match ? rcu_read_lock_held_common+0x12/0x50 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_bh_held+0xb0/0xb0 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_sched_held+0x5a/0xd0 ? lock_release+0xb9/0x400 ? lock_downgrade+0x390/0x390 ? ktime_get+0x64/0x130 ? ktime_get+0x8d/0x130 ? rcu_read_lock_held_common+0x12/0x50 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_held_common+0x12/0x50 ? rcu_read_lock_sched_held+0x5a/0xd0 ? rcu_read_lock_bh_held+0xb0/0xb0 ? rcu_read_lock_bh_held+0xb0/0xb0 __x64_sys_sendto+0x6f/0x80 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f1d126e4531 Code: 00 00 00 00 0f 1f 44 00 00 f3 0f 1e fa 48 8d 05 35 80 0c 00 41 89 ca 8b 00 85 c0 75 1c 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 67 c3 66 0f 1f 44 00 00 55 48 83 ec 20 48 89 RSP: 002b:00007ffe21a679d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 000000000000ffdc RCX: 00007f1d126e4531 RDX: 0000000000010000 RSI: 000000000374acf0 RDI: 0000000000000014 RBP: 00007ffe21a67ac0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
5th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 (6)

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

wifi: iwlwifi: mvm: fix double free on tx path. - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: iwlwifi: mvm: fix double free on tx path. - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: iwlwifi: mvm: fix double free on tx path. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fabe41fba907e4fd826acbbdb42e09c681c515e
Web page

wifi: iwlwifi: mvm: fix double free on tx path. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a2ecd1ec14075117ccb3e85f0fed224578ec228
Web page

wifi: iwlwifi: mvm: fix double free on tx path. - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: iwlwifi: mvm: fix double free on tx path. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0473cbae2137b963bd0eaa74336131cb1d3bc6c3

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.4.229 (fixes >=5.1.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 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 98 of 198 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-50248?
CVE-2022-50248 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: iwlwifi: mvm: fix double free on tx path. We see kernel crashes and lockups and KASAN errors related to ax210 firmware crashes. One of the KASAN dumps pointed at the tx path, and it appears there is indeed a way to…
When was the CVE record for CVE-2022-50248 published?
The CVE record for CVE-2022-50248 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-2022-50248 actively exploited?
CVE-2022-50248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50248?
CVE-2022-50248 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50248?
A fix for CVE-2022-50248 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-50248

Explore →

Is Your Infrastructure Affected by CVE-2022-50248?

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

Book a Demo →Browse All CVEs