Skip to main content
VulnerabilityPublished Updated

CVE-2026-53070: Linux kernel · sctp: disable BH before calling udp_tunnel_xmit_skb()

Source GCVE Database

0
Authoritative record:CVE-2026-53070· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in be3bfcb34bda04f6a350710db471d4133f950f2c : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in be3bfcb34bda04f6a350710db471d4133f950f2c, 790093245e35040c2adb15f48970020425aa3f47, 7f0062c40781fe0a340965f5bb0816681982ff4c +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 046c052b475e7119b6a30e3483e2888fc606a2f8, < be3bfcb34bda04f6a350710db471d4133f950f2c
Fixed in
  • be3bfcb34bda04f6a350710db471d4133f950f2c
LinuxLinuxAffected
  • ≥ 046c052b475e7119b6a30e3483e2888fc606a2f8, < 790093245e35040c2adb15f48970020425aa3f47
Fixed in
  • 790093245e35040c2adb15f48970020425aa3f47
LinuxLinuxAffected
  • ≥ 046c052b475e7119b6a30e3483e2888fc606a2f8, < 7f0062c40781fe0a340965f5bb0816681982ff4c
Fixed in
  • 7f0062c40781fe0a340965f5bb0816681982ff4c
LinuxLinuxAffected
  • ≥ 046c052b475e7119b6a30e3483e2888fc606a2f8, < 2cd7e6971fc2787408ceef17906ea152791448cf
Fixed in
  • 2cd7e6971fc2787408ceef17906ea152791448cf
LinuxLinuxAffected
  • ≥ 046c052b475e7119b6a30e3483e2888fc606a2f8, < 0de7db2eb27e82b983157016fa604b1ba664ae5f
Fixed in
  • 0de7db2eb27e82b983157016fa604b1ba664ae5f
LinuxLinuxAffected
  • =5.11
Fixed in–

Description

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

References

Community reviews

Loading reviews…