CVE-2023-53426
published 2025-09-18CVE-2023-53426: 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…
PriorityP340high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.14%
3.9th percentile
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.
Affected
18 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.55-1 (bookworm) | linux 6.1.55-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 < 6436973164ea5506a495f39e56be5aea375e7832 | 6436973164ea5506a495f39e56be5aea375e7832 |
| linux | linux | >= 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 < 595931912357fa3507e522a7f8a0a76e423c23e4 | 595931912357fa3507e522a7f8a0a76e423c23e4 |
| linux | linux | >= 18b1ab7aa76bde181bdb1ab19a87fa9523c32f21 < 3e019d8a05a38abb5c85d4f1e85fda964610aa14 | 3e019d8a05a38abb5c85d4f1e85fda964610aa14 |
| linux | linux | >= 5.15.33 < 5.15.132 | 5.15.132 |
| linux | linux | >= 5.16.19 < 5.17 | 5.17 |
| linux | linux | >= 5.17.2 < 5.18 | 5.18 |
| linux | linux | >= ad7219cd8751bd258b9d1e69ae0654ec00f71875 < 5979985f2d6b565b6cf0f79a62670a2855c0e96c | 5979985f2d6b565b6cf0f79a62670a2855c0e96c |
| linux | linux_kernel | >= 0 < 6.1.55-1 | 6.1.55-1 |
| linux | linux_kernel | >= 0 < 6.5.6-1 | 6.5.6-1 |
| linux | linux_kernel | >= 0 < 6.5.6-1 | 6.5.6-1 |
| linux | linux_kernel | >= 5.15.33 < 5.15.132 | 5.15.132 |
| linux | linux_kernel | >= 5.16.19 < 5.17 | 5.17 |
| linux | linux_kernel | >= 5.17.2 < 6.1.54 | 6.1.54 |
| linux | linux_kernel | >= 6.2 < 6.5.4 | 6.5.4 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: Linux kernel: Denial of Service in xsk_diag due to use-after-free during socket cleanup
vendor_redhat·2025-09-18·CVSS 7.8
CVE-2023-53426 [HIGH] CWE-825 kernel: Linux kernel: Denial of Service in xsk_diag due to use-after-free during socket cleanup
kernel: Linux kernel: Denial of Service in xsk_diag due to use-after-free during socket cleanup
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 f
Debian
CVE-2023-53426: linux - In the Linux kernel, the following vulnerability has been resolved: xsk: Fix xs...
vendor_debian·2023·CVSS 7.8
CVE-2023-53426 [HIGH] CVE-2023-53426: linux - In the Linux kernel, the following vulnerability has been resolved: xsk: Fix xs...
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 signallin
OSV
CVE-2023-53426: 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
osv·2025-09-18·CVSS 7.8
CVE-2023-53426 [HIGH] CVE-2023-53426: 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
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 signallin
GHSA
GHSA-26wc-246g-r3wf: 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-fre
ghsa_unreviewed·2025-09-18
CVE-2023-53426 [HIGH] CWE-416 GHSA-26wc-246g-r3wf: 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-fre
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 signal
No detection rules found.
No public exploits indexed.
2025-09-18
Published