espintcp: remove encap socket caching to avoid reference leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · < 74fd327767fb784c5875cf7c4ba1217f26020943| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
espintcp: remove encap socket caching to avoid reference leak
The current scheme for caching the encap socket can lead to reference leaks when we try to delete the netns.
The reference chain is: xfrm_state -> enacp_sk -> netns
Since the encap socket is a userspace socket, it holds a reference on the netns. If we delete the espintcp state (through flush or individual delete) before removing the netns, the reference on the socket is dropped and the netns is correctly deleted. Otherwise, the netns may not be reachable anymore (if all processes within the ns have terminated), so we cannot delete the xfrm state to drop its reference on the socket.
This patch results in a small (~2% in my tests) performance regression.
A GC-type mechanism could be added for the socket cache, to clear references if the state hasn't been used "recently", but it's a lot more complex than just not caching the socket.
From the CVE record · Linux
The Linux kernel's espintcp socket caching can leak a network namespace reference if the namespace is deleted before its espintcp state is removed. This can prevent the namespace from being deleted; the input does not specify attacker access, authentication, or user-interaction requirements.
Engineers running Linux kernels with espintcp should check their versions against the vendor advisory; affected versions were not provided.