sctp: disable BH before calling udp_tunnel_xmit_skb()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 046c052b475e7119b6a30e3483e2888fc606a2f8 · < 2cd7e6971fc2787408ceef17906ea152791448cf| No fix yet |
| Linux Linux |
|
|
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:
From the CVE record · Linux
The Linux kernel's IPv4 and IPv6 SCTP-over-UDP transmit paths can move between CPUs while tracking transmit recursion. When SCTP over UDP is enabled, this can cause incorrect recursion detection and packet drops. The input does not specify authentication or user-interaction requirements.
Operators running Linux kernels with SCTP over UDP enabled should check their kernel; affected versions are not specified.