Answer in brief
CVE-2024-58053 records a Unknown severity vulnerability in rxrpc: Fix handling of received connection abort. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <9c6702260557c0183d8417c79a37777a3d3e58e8 || >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <5842ce7b120c65624052a8da04460d35b26caac0 || >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <96d1d927c4d03ee9dcee7640bca70b74e63504fc || >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <0e56ebde245e4799ce74d38419426f2a80d39950 | 9c6702260557c0183d8417c79a37777a3d3e58e8, 5842ce7b120c65624052a8da04460d35b26caac0, 96d1d927c4d03ee9dcee7640bca70b74e63504fc, 0e56ebde245e4799ce74d38419426f2a80d39950 |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
Mar 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-58053 records a Unknown severity vulnerability in rxrpc: Fix handling of received connection abort. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <9c6702260557c0183d8417c79a37777a3d3e58e8 || >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <5842ce7b120c65624052a8da04460d35b26caac0 || >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <96d1d927c4d03ee9dcee7640bca70b74e63504fc || >=248f219cb8bcbfbd7f132752d44afa2df7c241d1 <0e56ebde245e4799ce74d38419426f2a80d39950 | 9c6702260557c0183d8417c79a37777a3d3e58e8, 5842ce7b120c65624052a8da04460d35b26caac0, 96d1d927c4d03ee9dcee7640bca70b74e63504fc, 0e56ebde245e4799ce74d38419426f2a80d39950 |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
Mar 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.