CVE-2025-39703

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 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, hsr: reject HSR frame if skb can't hold tag

Receiving HSR frame with insufficient space to hold HSR tag in the skb can result in a crash (kernel BUG):

[ 45.390915] skbuff: skb_under_panic: text:ffffffff86f32cac len:26 put:14 head:ffff888042418000 data:ffff888042417ff4 tail:0xe end:0x180 dev:bridge_slave_1 [ 45.392559] ------------[ cut here ]------------ [ 45.392912] kernel BUG at net/core/skbuff.c:211! [ 45.393276] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI [ 45.393809] CPU: 1 UID: 0 PID: 2496 Comm: reproducer Not tainted 6.15.0 #12 PREEMPT(undef) [ 45.394433] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 45.395273] RIP: 0010:skb_panic+0x15b/0x1d0

[ 45.402911] Call Trace: [ 45.403105] [ 45.404470] skb_push+0xcd/0xf0 [ 45.404726] br_dev_queue_push_xmit+0x7c/0x6c0 [ 45.406513] br_forward_finish+0x128/0x260 [ 45.408483] __br_forward+0x42d/0x590 [ 45.409464] maybe_deliver+0x2eb/0x420 [ 45.409763] br_flood+0x174/0x4a0 [ 45.410030] br_handle_frame_finish+0xc7c/0x1bc0 [ 45.411618] br_handle_frame+0xac3/0x1230 [ 45.413674] __netif_receive_skb_core.constprop.0+0x808/0x3df0 [ 45.422966] __netif_receive_skb_one_core+0xb4/0x1f0 [ 45.424478] __netif_receive_skb+0x22/0x170 [ 45.424806] process_backlog+0x242/0x6d0 [ 45.425116] __napi_poll+0xbb/0x630 [ 45.425394] net_rx_action+0x4d1/0xcc0 [ 45.427613] handle_softirqs+0x1a4/0x580 [ 45.427926] do_softirq+0x74/0x90 [ 45.428196]

This issue was found by syzkaller.

The panic happens in br_dev_queue_push_xmit() once it receives a corrupted skb with ETH header already pushed in linear data. When it attempts the skb_push() call, there's not enough headroom and skb_push() panics.

The corrupted skb is put on the queue by HSR layer, which makes a sequence of unintended transformations when it receives a specific corrupted HSR frame (with incomplete TAG).

Fix it by dropping and consuming frames that are not long enough to contain both ethernet and hsr headers.

Alternative fix would be to check for enough headroom before skb_push() in br_dev_queue_push_xmit().

In the reproducer, this is injected via AF_PACKET, but I don't easily see why it couldn't be sent over the wire from adjacent network.

Further Details:

In the reproducer, the following network interface chain is set up:

┌────────────────┐ ┌────────────────┐ │ veth0_to_hsr ├───┤ hsr_slave0 ┼───┐ └────────────────┘ └────────────────┘ │ │ ┌──────┐ ├─┤ hsr0 ├───┐ │ └──────┘ │ ┌────────────────┐ ┌────────────────┐ │ │┌────────┐ │ veth1_to_hsr ┼───┤ hsr_slave1 ├───┘ └┤ │ └────────────────┘ └────────────────┘ ┌┼ bridge │ ││ │ │└────────┘ │ ┌───────┐ │ │ ... ├──────┘ └───────┘

To trigger the events leading up to crash, reproducer sends a corrupted HSR fr ---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
4%
KEV
Not listed

Published

September 5, 2025

Last Modified

July 30, 2026

Vendor Advisories for CVE-2025-39703(1)

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

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-realtime-5.15 (5.15.0.1096.100) @ jammy2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1061 (5.15.0-1061.65) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-21ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1089.85) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1101.99) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-05-21ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1091.89) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1097.87) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-21ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
linuxKernel @ 5.10.241osv

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 9× in last 7d / 42× 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 125 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-39703?
CVE-2025-39703 is a medium vulnerability published on September 5, 2025. In the Linux kernel, the following vulnerability has been resolved: net, hsr: reject HSR frame if skb can't hold tag Receiving HSR frame with insufficient space to hold HSR tag in the skb can result in a crash (kernel BUG): [ 45.390915] skbuff: skbunderpanic: text:ffffffff86f32cac len:26 put:14…
When was CVE-2025-39703 disclosed?
CVE-2025-39703 was first published in the National Vulnerability Database on September 5, 2025, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-39703 actively exploited?
CVE-2025-39703 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 95.5% of all scored CVEs.
What is the CVSS score of CVE-2025-39703?
CVE-2025-39703 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-39703?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39703, 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-39703

Explore →

Is Your Infrastructure Affected by CVE-2025-39703?

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