CVE-2025-21663

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

January 21, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

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
generic

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
generic

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 / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-05-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-05-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-05-30ubuntu
ubuntulinux-virtual (6.8.0-60.63) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime (6.8.1-1022.23) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1028.31.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1028.28) @ noble2026-05-30ubuntu
ubuntulinux-tools-gke (6.8.0-1025.29) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1016.17) @ noble2026-05-30ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1012.14) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-60.63~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1026.27~22.04.1) @ jammy2026-05-30ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 6.6.72—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.

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 10× in last 7d / 45× 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 115 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-21663?
CVE-2025-21663 is a medium vulnerability 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 MGBEWRAPAXIASID0CTRL register. The current driver is hard coded to use MGBE0's…
When was CVE-2025-21663 disclosed?
CVE-2025-21663 was first published in the National Vulnerability Database on January 21, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21663 actively exploited?
CVE-2025-21663 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 66.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21663, 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-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.

Start Free Scan →Browse All CVEs