CVE-2026-53070

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

sctp: disable BH before calling udp_tunnel_xmit_skb()

udp_tunnel_xmit_skb() / udp_tunnel6_xmit_skb() are expected to run with BH disabled. After commit 6f1a9140ecda ("add xmit recursion limit to tunnel xmit functions"), on the path:

udp(6)_tunnel_xmit_skb() -> ip(6)tunnel_xmit()

dev_xmit_recursion_inc()/dec() must stay balanced on the same CPU.

Without local_bh_disable(), the context may move between CPUs, which can break the inc/dec pairing. This may lead to incorrect recursion level detection and cause packets to be dropped in ip(6)_tunnel_xmit() or __dev_queue_xmit().

Fix it by disabling BH around both IPv4 and IPv6 SCTP UDP xmit paths.

In my testing, after enabling the SCTP over UDP:

# ip net exec ha sysctl -w net.sctp.udp_port=9899 # ip net exec ha sysctl -w net.sctp.encap_port=9899 # ip net exec hb sysctl -w net.sctp.udp_port=9899 # ip net exec hb sysctl -w net.sctp.encap_port=9899

# ip net exec ha iperf3 -s

  • without this patch:

# ip net exec hb iperf3 -c 192.168.0.1 --sctp [ 5] 0.00-10.00 sec 37.2 MBytes 31.2 Mbits/sec sender [ 5] 0.00-10.00 sec 37.1 MBytes 31.1 Mbits/sec receiver

  • with this patch:

# ip net exec hb iperf3 -c 192.168.0.1 --sctp [ 5] 0.00-10.00 sec 3.14 GBytes 2.69 Gbits/sec sender [ 5] 0.00-10.00 sec 3.14 GBytes 2.69 Gbits/sec receiver

CVSS v3
7.5
EG Score
7.5(high)
EPSS
27.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 4, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

sctp: disable BH before calling udp_tunnel_xmit_skb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/790093245e35040c2adb15f48970020425aa3f47
generic

sctp: disable BH before calling udp_tunnel_xmit_skb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2cd7e6971fc2787408ceef17906ea152791448cf
generic

sctp: disable BH before calling udp_tunnel_xmit_skb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0de7db2eb27e82b983157016fa604b1ba664ae5f

Vendor Advisories for CVE-2026-53070(2)

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

Data Freshness Timeline

(refreshed 37× in last 7d / 51× 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.

  1. 2026-07-07 04:12 UTCEG score recompute
  2. 2026-07-07 04:12 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:44 UTCEG score recompute
  6. 2026-07-06 15:44 UTCGHSA enrichment
  7. 2026-07-06 03:16 UTCEG score recompute
  8. 2026-07-06 03:15 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 14:45 UTCEG score recompute
  12. 2026-07-05 14:45 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:12 UTCEG score recompute
  16. 2026-07-05 02:12 UTCGHSA enrichment
  17. 2026-07-04 13:44 UTCEG score recompute
  18. 2026-07-04 13:44 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 01:17 UTCEG score recompute
  21. 2026-07-04 01:17 UTCGHSA enrichment
  22. 2026-07-03 12:50 UTCEG score recompute
  23. 2026-07-03 12:49 UTCGHSA enrichment
  24. 2026-07-03 00:15 UTCEG score recompute
  25. 2026-07-03 00:14 UTCGHSA enrichment
Show 26 more
  1. 2026-07-02 11:48 UTCEG score recompute
  2. 2026-07-02 11:48 UTCGHSA enrichment
  3. 2026-07-01 23:21 UTCEG score recompute
  4. 2026-07-01 23:21 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 10:53 UTCEG score recompute
  7. 2026-07-01 10:53 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 22:25 UTCEG score recompute
  10. 2026-06-30 22:25 UTCGHSA enrichment
  11. 2026-06-30 09:59 UTCEG score recompute 7.50
  12. 2026-06-30 09:58 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 14:06 UTCEG score recompute
  20. 2026-06-27 14:06 UTCGHSA enrichment
  21. 2026-06-27 11:37 UTCNVD update
  22. 2026-06-27 10:39 UTCMITRE cvelistV5
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 18:15 UTCEG score recompute
  26. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53070?
CVE-2026-53070 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: disable BH before calling udptunnelxmit_skb() udptunnelxmitskb() / udptunnel6xmitskb() are expected to run with BH disabled. After commit 6f1a9140ecda ("add xmit recursion limit to tunnel xmit functions"), on the path:…
When was CVE-2026-53070 disclosed?
CVE-2026-53070 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53070 actively exploited?
CVE-2026-53070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53070?
CVE-2026-53070 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53070, 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-2026-53070

Explore →

Is Your Infrastructure Affected by CVE-2026-53070?

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