Log in Start free

Vulnerability · Published Sep 15, 2025 · Assigned by Linux

CVE-2023-53218rxrpc: Make it so that a waiting process can be aborted

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 6% 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 94.1% 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: rxrpc: Make it so that a waiting process can be aborted When sendmsg() creates an rxrpc call, it queues it to wait for a connection and channel to be assigned and then waits before it can start shovelling data as the encrypted DATA packet content includes a summary of the connection parameters. However, sendmsg() may get interrupted before a connection gets assigned and further sendmsg() calls will fail with EBUSY until an assignment is made. Fix this so that the call can at least be aborted without failing on EBUSY. We have to be careful here as sendmsg() mustn't be allowed to start the call timer if the call doesn't yet have a connection assigned as an oops may follow shortly thereafter.

Affected packages & fixed versions

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

Affected products (as reported)

VendorProductVersions
Linux Linux 540b1c48c37ac0ad66212004db21e1ff7e2d78be – before 7161cf61c64e9e9413d790f2fa2b9dada71a2249540b1c48c37ac0ad66212004db21e1ff7e2d78be – before 876d96faacbc407daf4978d7ec95051b68f5344a540b1c48c37ac0ad66212004db21e1ff7e2d78be – before 0eb362d254814ce04848730bf32e75b8ee1a4d6c
Linux Linux 4.11

References