In the Linux kernel, the RXRPC subsystem was found to process RESPONSE packets after the service challenge phase had ended. The code change added a state check to ensure such packets are only handled while the connection remained in RXRPC_CONN_SERVICE_CHALLENGING. Based on the description, it is inferred that the original flaw allowed duplicate or late RESPONSE frames to retrigger the connection‑setup routine, potentially leading to repeated resource usage or misconfiguration. These effects could degrade service availability.

Any Linux kernel that contains the unpatched RXRPC code is potentially affected, regardless of distribution. The advisory lists kernel commits that apply the fix; affected releases include any mainline kernel prior to the patch and the forthcoming stable series. System administrators should verify the current kernel version against the commit refs provided in the advisory.

The CVSS score of 7.5 classifies it as high severity. The EPSS probability is less than 1% indicating a low likelihood of exploitation in the wild. The vulnerability is not listed in CISA’s KEV catalog. The CVE description suggests that an attacker would need the ability to send crafted RXRPC RESPONSE packets to a target while it’s handling a challenge. It is inferred that the attack vector relies on remote network access to deliver these packets. Because the flaw can lead to repeated handling processes, the potential impact may manifest as availability degradation of the affected services.