Review reviewHigh

CVE-2026-53070

Linux Linux, linux kernel

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 dropp...

CVSS
7.5
EPSS
0.35%
27.2% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.35%
Technical severityCVSS 7.5

Vulnerability overview

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 dropp...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 046c052b475e7119b6a30e3483e2888fc606a2f8 < be3bfcb34bda04f6a350710db471d4133f950f2c, >= 046c052b475e7119b6a30e3483e2888fc606a2f8 < 0de7db2eb27e82b983157016fa604b1ba664ae5f, >= 046c052b475e7119b6a30e3483e2888fc606a2f8 < 790093245e35040c2adb15f48970020425aa3f47, >= 046c052b475e7119b6a30e3483e2888fc606a2f8 < 2cd7e6971fc2787408ceef17906ea152791448cf, >= 5.11, >= 5.11 < 6.12.95, >= 6.13 < 6.18.37, >= 6.19 < 7.0.10
Fixed versions
6.12.95, 6.18.37, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
Not available