CVE-2025-21663

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-01-21. 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-2612 (ENISA EUVD) · GHSA-42xc-c24r-x3cc (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.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: stmmac: dwmac-tegra: Read iommu stream id from device tree

Nvidia's Tegra MGBE controllers require the IOMMU "Stream ID" (SID) to be written to the MGBE_WRAP_AXI_ASID0_CTRL register.

The current driver is hard coded to use MGBE0's SID for all controllers. This causes softirq time outs and kernel panics when using controllers other than MGBE0.

Example dmesg errors when an ethernet cable is connected to MGBE1:

[ 116.133290] tegra-mgbe 6910000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx [ 121.851283] tegra-mgbe 6910000.ethernet eth1: NETDEV WATCHDOG: CPU: 5: transmit queue 0 timed out 5690 ms [ 121.851782] tegra-mgbe 6910000.ethernet eth1: Reset adapter. [ 121.892464] tegra-mgbe 6910000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 121.905920] tegra-mgbe 6910000.ethernet eth1: PHY [stmmac-1:00] driver [Aquantia AQR113] (irq=171) [ 121.907356] tegra-mgbe 6910000.ethernet eth1: Enabling Safety Features [ 121.907578] tegra-mgbe 6910000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported [ 121.908399] tegra-mgbe 6910000.ethernet eth1: registered PTP clock [ 121.908582] tegra-mgbe 6910000.ethernet eth1: configuring for phy/10gbase-r link mode [ 125.961292] tegra-mgbe 6910000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx [ 181.921198] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 181.921404] rcu: 7-....: (1 GPs behind) idle=540c/1/0x4000000000000002 softirq=1748/1749 fqs=2337 [ 181.921684] rcu: (detected by 4, t=6002 jiffies, g=1357, q=1254 ncpus=8) [ 181.921878] Sending NMI from CPU 4 to CPUs 7: [ 181.921886] NMI backtrace for cpu 7 [ 181.922131] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Kdump: loaded Not tainted 6.13.0-rc3+ #6 [ 181.922390] Hardware name: NVIDIA CTI Forge + Orin AGX/Jetson, BIOS 202402.1-Unknown 10/28/2024 [ 181.922658] pstate: 40400009 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 181.922847] pc : handle_softirqs+0x98/0x368 [ 181.922978] lr : __do_softirq+0x18/0x20 [ 181.923095] sp : ffff80008003bf50 [ 181.923189] x29: ffff80008003bf50 x28: 0000000000000008 x27: 0000000000000000 [ 181.923379] x26: ffffce78ea277000 x25: 0000000000000000 x24: 0000001c61befda0 [ 181.924486] x23: 0000000060400009 x22: ffffce78e99918bc x21: ffff80008018bd70 [ 181.925568] x20: ffffce78e8bb00d8 x19: ffff80008018bc20 x18: 0000000000000000 [ 181.926655] x17: ffff318ebe7d3000 x16: ffff800080038000 x15: 0000000000000000 [ 181.931455] x14: ffff000080816680 x13: ffff318ebe7d3000 x12: 000000003464d91d [ 181.938628] x11: 0000000000000040 x10: ffff000080165a70 x9 : ffffce78e8bb0160 [ 181.945804] x8 : ffff8000827b3160 x7 : f9157b241586f343 x6 : eeb6502a01c81c74 [ 181.953068] x5 : a4acfcdd2e8096bb x4 : ffffce78ea277340 x3 : 00000000ffffd1e1 [ 181.960329] x2 : 0000000000000101 x1 : ffffce78ea277340 x0 : ffff318ebe7d3000 [ 181.967591] Call trace: [ 181.970043] handle_softirqs+0x98/0x368 (P) [ 181.974240] __do_softirq+0x18/0x20 [ 181.977743] ____do_softirq+0x14/0x28 [ 181.981415] call_on_irq_stack+0x24/0x30 [ 181.985180] do_softirq_own_stack+0x20/0x30 [ 181.989379] __irq_exit_rcu+0x114/0x140 [ 181.993142] irq_exit_rcu+0x14/0x28 [ 181.996816] el1_interrupt+0x44/0xb8 [ 182.000316] el1h_64_irq_handler+0x14/0x20 [ 182.004343] el1h_64_irq+0x80/0x88 [ 182.007755] cpuidle_enter_state+0xc4/0x4a8 (P) [ 182.012305] cpuidle_enter+0x3c/0x58 [ 182.015980] cpuidle_idle_call+0x128/0x1c0 [ 182.020005] do_idle+0xe0/0xf0 [ 182.023155] cpu_startup_entry+0x3c/0x48 [ 182.026917] secondary_start_kernel+0xdc/0x120 [ 182.031379] __secondary_switched+0x74/0x78 [ 212.971162] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 7-.... } 6103 jiffies s: 417 root: 0x80/. [ 212.985935] rcu: blocking rcu_node structures (internal RCU debug): [ 212.992758] Sending NMI from CPU 0 to CPUs 7: [ 212.998539] NMI backtrace for cpu 7 [ 213.004304] CPU: 7 UID: 0 PI ---truncated---

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.4% × 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.4%
EPSS %ILE
35th
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.4% within 30 daysSource: FIRST EPSS. 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

January 21, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available.
Web page

net: stmmac: dwmac-tegra: Read iommu stream id from device tree - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: stmmac: dwmac-tegra: Read iommu stream id from device tree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/426046e2d62dd19533808661e912b8e8a9eaec16
Web page

net: stmmac: dwmac-tegra: Read iommu stream id from device tree - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/235419f0956e8c60e597aa1619ded8bda7460bb4

Vendor Advisories for CVE-2025-21663(1)

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

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-10-24ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-10-24ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-60.63~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1026.27~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual (6.8.0-60.63) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-10-24ubuntu
ubuntulinux-tools-realtime (6.8.1-1022.23) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1028.31~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gke (6.8.0-1025.29) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1029.34~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1016.17) @ noble2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1012.14) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-24ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.6.72 (fixes >=6.2.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.10-1: fixed in 6.12.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.10-1: fixed in 6.12.10-1
—

Additional Vendor Advisories

(16)

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 / 40× 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 204 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 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-21663?
CVE-2025-21663 is a medium-severity vulnerability; its CVE record was published on January 21, 2025. In the Linux kernel, the following vulnerability has been resolved: net: stmmac: dwmac-tegra: Read iommu stream id from device tree Nvidia's Tegra MGBE controllers require the IOMMU "Stream ID" (SID) to be written to the MGBE_WRAP_AXI_ASID0_CTRL register. The current driver is hard coded to use…
When was the CVE record for CVE-2025-21663 published?
The CVE record for CVE-2025-21663 was published on January 21, 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-21663 actively exploited?
CVE-2025-21663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21663?
CVE-2025-21663 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21663?
A fix for CVE-2025-21663 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21663 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-21663

Explore →

Is Your Infrastructure Affected by CVE-2025-21663?

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

Book a Demo →Browse All CVEs