Vulnerability · Published May 2, 2025 · Assigned by Linux

CVE-2023-53072mptcp: use the workqueue to destroy unaccepted sockets

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 89.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: mptcp: use the workqueue to destroy unaccepted sockets Christoph reported a UaF at token lookup time after having refactored the passive socket initialization part: BUG: KASAN: use-after-free in __token_bucket_busy+0x253/0x260 Read of size 4 at addr ffff88810698d5b0 by task syz-executor653/3198 CPU: 1 PID: 3198 Comm: syz-executor653 Not tainted 6.2.0-rc59af4eaa31c1f6c00c8f1e448ed99a45c66340dd5 #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x6e/0x91 print_report+0x16a/0x46f kasan_report+0xad/0x130 __token_bucket_busy+0x253/0x260 mptcp_token_new_connect+0x13d/0x490 mptcp_connect+0x4ed/0x860 __inet_stream_connect+0x80e/0xd90 tcp_sendmsg_fastopen+0x3ce/0x710 mptcp_sendmsg+0xff1/0x1a20 inet_sendmsg+0x11d/0x140 __sys_sendto+0x405/0x490 __x64_sys_sendto+0xdc/0x1b0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc We need to properly clean-up all the paired MPTCP-level resources and be sure to release the msk last, even when the unaccepted subflow is destroyed by the TCP internals via inet_child_forget(). We can re-use the existing MPTCP_WORK_CLOSE_SUBFLOW infra, explicitly checking that for the critical scenario: the closed subflow is the MPC one, the msk is not accepted and eventually going through full cleanup. With such change, __mptcp_destroy_sock() is always called on msk sockets, even on accepted ones. We don't need anymore to transiently drop one sk reference at msk clone time. Please note this commit depends on the parent one: mptcp: refactor passive socket initialization

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.25-1DEBIAN-CVE-2023-53072
Debian:13linux6.1.25-1DEBIAN-CVE-2023-53072
Debian:14linux6.1.25-1DEBIAN-CVE-2023-53072
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2023-53072
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53072
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53072
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2023-53072

Affected products (as reported)

VendorProductVersions
Linux Linux 58b09919626bf9067345289212ec030c61eb1034 – before 2827f099b3fb9a59263c997400e9182f5d423e8458b09919626bf9067345289212ec030c61eb1034 – before 804cf487fb0031f3c74755b78d8663333f0ba63658b09919626bf9067345289212ec030c61eb1034 – before b6985b9b82954caa53f862d6059d06c0526254f0
Linux Linux 5.7

References