Answer in brief
CVE-2024-49864 records a High severity (CVSS 7.5) vulnerability in rxrpc: Fix a race between socket set up and I/O thread creation. 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.
CVSS is 7.5. 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 | >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <cdf4bbbdb956d7426f687f38757ebca2a2759a0f || >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <56e415202b8a17de6496f4023e545fcb66f118ec || >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <c64f5fc95e9612fdf75587c8e21e494e614c18e2 || >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <bc212465326e8587325f520a052346f0b57360e6 | cdf4bbbdb956d7426f687f38757ebca2a2759a0f, 56e415202b8a17de6496f4023e545fcb66f118ec, c64f5fc95e9612fdf75587c8e21e494e614c18e2, bc212465326e8587325f520a052346f0b57360e6 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Oct 21, 2024
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 a race between socket set up and I/O thread creation In rxrpc_open_socket(), it sets up the socket and then sets up the I/O thread that will handle it. This is a problem, however, as there's a gap between the two phases in which a packet may come into rxrpc_encap_rcv() from the UDP packet but we oops when trying to wake the not-yet created I/O thread. As a quick fix, just make rxrpc_encap_rcv() discard the packet if there's no I/O thread yet. A better, but more intrusive fix would perhaps be to rearrange things such that the socket creation is done by the I/O thread.
Quoted source text, attributed separately from HOL analysis.