LiveActive security incident?Get immediate response
CVE Record

CVE-2024-39293: Revert "xsk: Support redirect to any socket bound to the same umem"

In the Linux kernel, the following vulnerability has been resolved: Revert "xsk: Support redirect to any socket bound to the same umem" This reverts commit 2863d665ea41282379f108e4da6c8a2366ba66db. This patch introduced a potential kernel crash when multiple napi instances redirect to the same AF_XDP socket. By removing the queue_index check, it is possible for multiple napi instances to access the Rx ring at the same time, which will result in a corrupted ring state which can lead to a crash when flushing the rings in __xsk_flush(). This can happen when the linked list of sockets to flush gets corrupted by concurrent accesses. A quick and small fix is not possible, so let us revert this for now.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems using AF_XDP packet processing when multiple NAPI contexts redirect traffic to the same socket. The business impact is availability risk on high-performance networking hosts. The provided sources do not show active exploitation or a CVSS score.

Executive priority

Treat as a targeted availability risk for Linux network-processing infrastructure. Patch through normal kernel maintenance, with higher urgency for packet capture, filtering, DDoS, load balancing, or trading systems using AF_XDP/XDP.

Technical view

A reverted xsk change removed a queue_index check, allowing concurrent access to an AF_XDP socket Rx ring by multiple NAPI instances. That can corrupt ring state and the socket flush list, causing a crash in __xsk_flush(). The kernel fix reverts the problematic commit.

Likely exposure

Exposure is most likely on Linux systems running affected 6.9-era kernels with AF_XDP/XDP networking paths in use. The source bundle identifies Linux 6.9, 6.9.5, and 6.10 context, but exact downstream distro exposure requires vendor kernel mapping.

Exploitation context

The bundle reports no CISA KEV listing and provides no evidence of active exploitation. The described failure requires a concurrency condition involving multiple NAPI instances redirecting to the same AF_XDP socket, which suggests operational availability impact rather than confirmed remote compromise.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. No exploit details, CVSS, CWE, or KEV signal are provided. Analysis should focus on kernel version lineage, AF_XDP usage, and whether downstream kernels include the revert.

Mitigation direction

  • Update to a kernel containing the referenced stable revert commits.
  • Check your Linux distribution advisory for the fixed kernel package.
  • Prioritize hosts using AF_XDP, XDP, or high-performance packet processing.
  • Consider reducing affected AF_XDP redirection patterns until patched.
  • Monitor for kernel crashes involving __xsk_flush or AF_XDP paths.

Validation and detection

  • Inventory kernel versions on Linux networking hosts.
  • Identify systems using AF_XDP, XDP, or custom packet processing.
  • Confirm vendor kernel builds include the stable revert.
  • Review crash logs for __xsk_flush, xsk, or AF_XDP references.
  • Retest packet-processing workloads after the kernel update.
Prepared
Confidence
medium
Sources
4

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-39293 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
2ADP providers
3Source links

SSVC decision data

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

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
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2863d665ea41282379f108e4da6c8a2366ba66db, 2863d665ea41282379f108e4da6c8a2366ba66dbunaffected
LinuxLinux6.9, 0, 6.9.5, 6.10affected
Weakness

CWE details

No CWE listed

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