CVE-2024-58053 is a vulnerability identified in the Linux kernel's rxrpc protocol implementation. The issue pertains to improper handling of received connection abort signals at the connection level. Specifically, when a connection abort is received, the kernel propagates this abort to the calls associated with that connection. However, the calls are not properly woken up to process their termination. As a result, these calls hang indefinitely because no further input is received to trigger their completion or cleanup. This flaw can lead to resource exhaustion or denial of service conditions within the kernel's networking stack. The fix involves correcting the propagation mechanism to ensure that calls are properly notified and can terminate gracefully. Additionally, tracing has been added to improve logging of connection abort events, aiding in diagnostics and monitoring. The vulnerability affects Linux kernel versions identified by the commit hash 248f219cb8bcbfbd7f132752d44afa2df7c241d1, indicating a specific code state rather than a broad version range. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

For European organizations, this vulnerability could impact any systems running affected Linux kernel versions that utilize the rxrpc protocol, which is commonly used in distributed computing environments and certain enterprise applications. The hanging calls caused by improper abort handling can lead to denial of service conditions, potentially disrupting critical services or applications relying on these kernel networking features. This could degrade system availability and reliability, impacting business operations, especially in sectors with high dependence on Linux-based infrastructure such as telecommunications, cloud service providers, and research institutions. Although no active exploitation is known, the vulnerability could be leveraged by attackers to cause service interruptions or to facilitate further attacks by destabilizing systems. The impact is primarily on availability, with limited direct confidentiality or integrity risks, but service disruption in critical environments can have significant operational consequences.

Organizations should promptly identify Linux systems running the affected kernel commit or versions derived from it. Applying the official kernel patch that fixes the rxrpc connection abort handling is the primary mitigation step. Since this vulnerability relates to kernel-level networking, updating to the latest stable Linux kernel release that includes this fix is recommended. For environments where immediate patching is challenging, monitoring kernel logs for connection abort events and anomalous hanging calls can help detect potential exploitation attempts or system instability. Network segmentation and limiting exposure of services using rxrpc can reduce attack surface. Additionally, organizations should maintain robust incident response plans to quickly address any denial of service symptoms. Testing patches in staging environments before deployment is advised to ensure compatibility and stability.