LiveActive security incident?Get immediate response
CVE Record

CVE-2024-49864: rxrpc: Fix a race between socket set up and I/O thread creation

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A timing flaw in the Linux RxRPC networking code can cause the kernel to crash when a packet arrives after socket setup but before its I/O thread exists. The documented impact is loss of availability, not data theft or modification. Systems using an affected kernel and RxRPC warrant prompt assessment.

Executive priority

Prioritize remediation for critical or network-exposed Linux systems after confirming RxRPC relevance. The principal business risk is service interruption or host instability. Because the version data is incomplete and exploitation is not documented, use targeted urgent patching rather than declaring an organization-wide emergency without exposure validation.

Technical view

The race occurs between socket initialization in rxrpc_open_socket() and I/O-thread creation. A UDP packet reaching rxrpc_encap_rcv() during this window may trigger an invalid wake-up and kernel oops. The stable fix discards packets received before the I/O thread exists. CVSS 3.1 is 7.5: network-accessible, low complexity, unauthenticated, and availability-only.

Likely exposure

Exposure is most plausible on systems running affected Linux kernel versions where RxRPC is present and can receive traffic during socket initialization. The supplied version metadata lists 6.2, 6.6.55, 6.10.14, 6.11.3, and 6.12, but is ambiguous; confirm exact distribution package status against vendor guidance and the referenced stable commits.

Exploitation context

The CVSS vector indicates a remotely reachable, unauthenticated availability risk with low attack complexity. However, the bundle marks this CVE as absent from KEV and supplies no evidence of active exploitation or a public exploit. Treat exploit prevalence as unknown rather than assuming exploitation is occurring.

Researcher notes

The fix is intentionally narrow: rxrpc_encap_rcv() drops a packet when no I/O thread exists. The disclosure notes that moving socket creation into the I/O thread might be a more complete but intrusive design. No CWE, proof of concept, attack observations, or distribution-specific fixed-package mappings are provided.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable referenced stable fix.
  • Use distribution security guidance to map fixed commits to packaged kernel versions.
  • Prioritize externally reachable or operationally critical systems using RxRPC.
  • Apply normal kernel-update procedures, including rebooting into the corrected kernel.

Validation and detection

  • Inventory running kernel versions, not only installed kernel packages.
  • Determine whether affected systems use or expose RxRPC-related functionality.
  • Verify the running kernel package incorporates an applicable referenced fix commit.
  • Confirm systems rebooted successfully into the corrected kernel.
  • Review kernel logs for relevant oops or unexpected availability events.
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-49864 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

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

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-49864Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa275da62e8c111b897b9cb73eb91df2f4e475ca5, a275da62e8c111b897b9cb73eb91df2f4e475ca5, a275da62e8c111b897b9cb73eb91df2f4e475ca5, a275da62e8c111b897b9cb73eb91df2f4e475ca5unaffected
LinuxLinux6.2, 0, 6.6.55, 6.10.14, 6.11.3, 6.12affected
Weakness

CWE details

No CWE listed

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