Answer in brief
CVE-2024-39293 records a Unknown severity vulnerability in Revert "xsk: Support redirect to any socket bound to the same umem". 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 | >=2863d665ea41282379f108e4da6c8a2366ba66db <19cb40b1064566ea09538289bfcf5bc7ecb9b6f5 || >=2863d665ea41282379f108e4da6c8a2366ba66db <7fcf26b315bbb728036da0862de6b335da83dff2 | 19cb40b1064566ea09538289bfcf5bc7ecb9b6f5, 7fcf26b315bbb728036da0862de6b335da83dff2 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jun 25, 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: 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-39293 records a Unknown severity vulnerability in Revert "xsk: Support redirect to any socket bound to the same umem". 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 | >=2863d665ea41282379f108e4da6c8a2366ba66db <19cb40b1064566ea09538289bfcf5bc7ecb9b6f5 || >=2863d665ea41282379f108e4da6c8a2366ba66db <7fcf26b315bbb728036da0862de6b335da83dff2 | 19cb40b1064566ea09538289bfcf5bc7ecb9b6f5, 7fcf26b315bbb728036da0862de6b335da83dff2 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jun 25, 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: 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.
Quoted source text, attributed separately from HOL analysis.