CVE-2026-53070

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

Published

June 24, 2026

Last Modified

August 5, 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.

Patch Availability(8)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 5× in last 7d / 83× 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 260 total refreshes for this CVE.

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

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 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-2026-53070 actively exploited?
CVE-2026-53070 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 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53070?
CVE-2026-53070 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.