LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58053: rxrpc: Fix handling of received connection abort

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix handling of received connection abort Fix the handling of a connection abort that we've received. Though the abort is at the connection level, it needs propagating to the calls on that connection. Whilst the propagation bit is performed, the calls aren't then woken up to go and process their termination, and as no further input is forthcoming, they just hang. Also add some tracing for the logging of connection aborts.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can leave rxrpc calls hanging after a connection-level abort is received. In business terms, affected systems using rxrpc-dependent functionality could experience stuck operations or service degradation. The public record does not provide a CVSS score, impact rating, or evidence of active exploitation.

Executive priority

Track and remediate through normal Linux kernel patch governance, escalating for systems that depend on rxrpc-related functionality. Current evidence does not justify emergency treatment without local exposure or vendor severity signals.

Technical view

The flaw is in Linux kernel rxrpc connection-abort handling. The abort state is propagated to calls on the connection, but those calls are not woken to process termination, so they can hang when no further input arrives. Stable kernel commits address the handling and add tracing for connection abort logging.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions and using rxrpc-related functionality, such as kernel components or services depending on AF_RXRPC. The bundle does not prove exposure for all Linux hosts.

Exploitation context

The provided sources do not show KEV listing, public exploitation, exploit maturity, or a complete attack scenario. Treat this as a reliability and availability concern until vendor advisories provide stronger severity context.

Researcher notes

Key uncertainty is impact scope. The record describes a hang caused by missed wakeups after received connection aborts, but lacks CVSS, CWE, exploit details, and product-specific advisories. Validate against vendor kernel backports rather than raw upstream version strings alone.

Mitigation direction

  • Apply Linux kernel vendor updates that include the referenced stable fixes.
  • Check distribution advisories for backported fixes and exact package versions.
  • Prioritize systems that use rxrpc-dependent services or kernel features.
  • If patching is delayed, follow vendor guidance for reducing rxrpc-related exposure.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify systems using rxrpc, AF_RXRPC, or dependent services.
  • Confirm whether vendor kernel packages include the referenced stable commits.
  • Monitor affected systems for stuck rxrpc or AFS-related operations.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-58053 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux248f219cb8bcbfbd7f132752d44afa2df7c241d1, 248f219cb8bcbfbd7f132752d44afa2df7c241d1, 248f219cb8bcbfbd7f132752d44afa2df7c241d1, 248f219cb8bcbfbd7f132752d44afa2df7c241d1unaffected
LinuxLinux4.9, 0, 6.6.76, 6.12.13, 6.13.2, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.