CVE-2025-22102

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-04-16. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2025-11210 (ENISA EUVD) · GHSA-23cf-whmv-wf37 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: btnxpuart: Fix kernel panic during FW release

This fixes a kernel panic seen during release FW in a stress test scenario where WLAN and BT FW download occurs simultaneously, and due to a HW bug, chip sends out only 1 bootloader signatures.

When driver receives the bootloader signature, it enters FW download mode, but since no consequtive bootloader signatures seen, FW file is not requested.

After 60 seconds, when FW download times out, release_firmware causes a kernel panic.

[ 2601.949184] Unable to handle kernel paging request at virtual address 0000312e6f006573 [ 2601.992076] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000111802000 [ 2601.992080] [0000312e6f006573] pgd=0000000000000000, p4d=0000000000000000 [ 2601.992087] Internal error: Oops: 0000000096000021 [#1] PREEMPT SMP [ 2601.992091] Modules linked in: algif_hash algif_skcipher af_alg btnxpuart(O) pciexxx(O) mlan(O) overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce snd_soc_fsl_easrc snd_soc_fsl_asoc_card imx8_media_dev(C) snd_soc_fsl_micfil polyval_generic snd_soc_fsl_xcvr snd_soc_fsl_sai snd_soc_imx_audmux snd_soc_fsl_asrc snd_soc_imx_card snd_soc_imx_hdmi snd_soc_fsl_aud2htx snd_soc_fsl_utils imx_pcm_dma dw_hdmi_cec flexcan can_dev [ 2602.001825] CPU: 2 PID: 20060 Comm: hciconfig Tainted: G C O 6.6.23-lts-next-06236-gb586a521770e #1 [ 2602.010182] Hardware name: NXP i.MX8MPlus EVK board (DT) [ 2602.010185] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2602.010191] pc : _raw_spin_lock+0x34/0x68 [ 2602.010201] lr : free_fw_priv+0x20/0xfc [ 2602.020561] sp : ffff800089363b30 [ 2602.020563] x29: ffff800089363b30 x28: ffff0000d0eb5880 x27: 0000000000000000 [ 2602.020570] x26: 0000000000000000 x25: ffff0000d728b330 x24: 0000000000000000 [ 2602.020577] x23: ffff0000dc856f38 [ 2602.033797] x22: ffff800089363b70 x21: ffff0000dc856000 [ 2602.033802] x20: ff00312e6f006573 x19: ffff0000d0d9ea80 x18: 0000000000000000 [ 2602.033809] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaad80dd480 [ 2602.083320] x14: 0000000000000000 x13: 00000000000001b9 x12: 0000000000000002 [ 2602.083326] x11: 0000000000000000 x10: 0000000000000a60 x9 : ffff800089363a30 [ 2602.083333] x8 : ffff0001793d75c0 x7 : ffff0000d6dbc400 x6 : 0000000000000000 [ 2602.083339] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : 0000000000000001 [ 2602.083346] x2 : 0000000000000000 x1 : 0000000000000001 x0 : ff00312e6f006573 [ 2602.083354] Call trace: [ 2602.083356] _raw_spin_lock+0x34/0x68 [ 2602.083364] release_firmware+0x48/0x6c [ 2602.083370] nxp_setup+0x3c4/0x540 [btnxpuart] [ 2602.083383] hci_dev_open_sync+0xf0/0xa34 [ 2602.083391] hci_dev_open+0xd8/0x178 [ 2602.083399] hci_sock_ioctl+0x3b0/0x590 [ 2602.083405] sock_do_ioctl+0x60/0x118 [ 2602.083413] sock_ioctl+0x2f4/0x374 [ 2602.091430] __arm64_sys_ioctl+0xac/0xf0 [ 2602.091437] invoke_syscall+0x48/0x110 [ 2602.091445] el0_svc_common.constprop.0+0xc0/0xe0 [ 2602.091452] do_el0_svc+0x1c/0x28 [ 2602.091457] el0_svc+0x40/0xe4 [ 2602.091465] el0t_64_sync_handler+0x120/0x12c [ 2602.091470] el0t_64_sync+0x190/0x194

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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
11th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-25). 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

April 16, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

Bluetooth: btnxpuart: Fix kernel panic during FW release - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: btnxpuart: Fix kernel panic during FW release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6749cf49eff7ce6dadcb603c5c8db70b28079a5d
Web page

Bluetooth: btnxpuart: Fix kernel panic during FW release - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: btnxpuart: Fix kernel panic during FW release - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2025-22102(1)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-24ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-24ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-24ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-24ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1043.44~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.92 (fixes >=6.4.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.30-1: fixed in 6.12.30-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.30-1: fixed in 6.12.30-1
—

Additional Vendor Advisories

(19)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× 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 96 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-22102?
CVE-2025-22102 is a medium-severity vulnerability; its CVE record was published on April 16, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btnxpuart: Fix kernel panic during FW release This fixes a kernel panic seen during release FW in a stress test scenario where WLAN and BT FW download occurs simultaneously, and due to a HW bug, chip sends out only 1…
When was the CVE record for CVE-2025-22102 published?
The CVE record for CVE-2025-22102 was published on April 16, 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-2025-22102 actively exploited?
CVE-2025-22102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-22102?
CVE-2025-22102 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-22102?
A fix for CVE-2025-22102 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-22102 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-2025-22102

Explore →

Is Your Infrastructure Affected by CVE-2025-22102?

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

Book a Demo →Browse All CVEs