xfrm: espintcp: fix UAF during close
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · < 24efebecf415ba264adba0f0491cec436463a14f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfrm: espintcp: fix UAF during close
ZDI reported and analyzed a race condition during close for espintcp sockets:
espintcp_close() frees emsg->skb via kfree_skb() without holding any socket lock. Concurrently, the xfrm_trans_reinject work queue invokes esp_output_tcp_finish() -> espintcp_push_skb() -> espintcp_push_msgs() -> skb_send_sock_locked(), which reads the same skb as a data source.
Fix this by adding a synchronize_rcu() call after resetting sk_prot, since esp_output_tcp_finish() runs under RCU and won't use a socket with sk_prot == &tcp_prot. Simply taking the socket lock in espintcp_close() could lead to leaks, if esp_output_tcp_finish() re-adds an skb in the slot we just freed. After this, the existing barrier() is no longer needed.
From the CVE record · Linux
A race in the Linux kernel's ESP-in-TCP socket close path can cause a use-after-free. It occurs when a socket closes while the xfrm_trans_reinject work queue reads the same packet buffer. The input does not specify how an attacker could trigger the race or whether authentication or user interaction is required.
Teams running Linux kernels with ESP-in-TCP support should check their kernel's status; affected versions are not specified.