xsk: Fix xsk_diag use-after-free error during socket cleanup

Summary

In the Linux kernel, the following vulnerability has been resolved: xsk: Fix xsk_diag use-after-free error during socket cleanup Fix a use-after-free error that is possible if the xsk_diag interface is used after the socket has been unbound from the device. This can happen either due to the socket being closed or the device disappearing. In the early days of AF_XDP, the way we tested that a socket was not bound to a device was to simply check if the netdevice pointer in the xsk socket structure was NULL. Later, a better system was introduced by having an explicit state variable in the xsk socket struct. For example, the state of a socket that is on the way to being closed and has been unbound from the device is XSK_UNBOUND. The commit in the Fixes tag below deleted the old way of signalling that a socket is unbound, setting dev to NULL. This in the belief that all code using the old way had been exterminated. That was unfortunately not true as the xsk diagnostics code was still using the old way and thus does not work as intended when a socket is going down. Fix this by introducing a test against the state variable. If the socket is in the state XSK_UNBOUND, simply abort the diagnostic's netlink operation.

Timeline

1. Sep 18, 2025, 4:04 PM UTCCVE published
2. Jan 14, 2026, 7:13 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Aug 5, 2026, 9:14 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 5.15.33 · fixed in 5.15.132; From 5.16.19 · fixed in 5.17; From 5.17.2 · fixed in 5.18

• Linux Linux

  5.18

References 4