sctp: close UDP tunnel sockets during netns teardown
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 046c052b475e7119b6a30e3483e2888fc606a2f8 · < ffb2bd7ade36ec4da32c46a6eddbf4515316d08c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: close UDP tunnel sockets during netns teardown
proc_sctp_do_udp_port() starts per-net SCTP UDP tunneling sockets when net.sctp.udp_port is set, and stops/restarts them when the sysctl value changes. The netns exit path does not stop these sockets, so a namespace can be torn down while its SCTP UDP tunnel sockets are still installed.
Close the UDP tunnel sockets from sctp_ctrlsock_exit() after unregistering the per-net sysctl table. This prevents new sysctl writes from racing in while the sockets are being released, and closes the sockets before the control socket is destroyed.
From the CVE record · Linux
The Linux kernel does not close per-network-namespace SCTP UDP tunnel sockets when a namespace is torn down. If SCTP UDP tunneling has been enabled through net.sctp.udp_port, those sockets can remain installed during teardown. The input does not describe an attacker action or specify whether network access, authentication, or user interaction is required.
Teams running Linux kernels that use SCTP UDP tunneling should check their versions against the vendor advisory; affected versions are not specified.