Answer in brief
CVE-2025-37920 records a Unknown severity vulnerability in xsk: Fix race condition in AF_XDP generic RX path. 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 | >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <975b372313dc018b9bd6cc0d85d188787054b19e || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <b6978c565ce33658543c637060852434b4248d30 || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <65d3c570614b892257dc58a1b202908242ecf8fd || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <75a240a3e8abf17b9e00b0ef0492b1bbaa932251 || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <a1356ac7749cafc4e27aa62c0c4604b5dca4983e || fd7c22ba7a0ad898b9ecf77dd53f5ccc48492e35 || 8a090e3b73eaffe18e08ccc3fb5abecf6b0a9781 || >=5.1.20 <5.2 || >=5.2.3 <5.3 | 975b372313dc018b9bd6cc0d85d188787054b19e, b6978c565ce33658543c637060852434b4248d30, 65d3c570614b892257dc58a1b202908242ecf8fd, 75a240a3e8abf17b9e00b0ef0492b1bbaa932251, a1356ac7749cafc4e27aa62c0c4604b5dca4983e, 5.2, 5.3 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
May 20, 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: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp socket from all maps and waits for completion of all outstanding rx operations. Packets in RX path will either complete safely or drop.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37920 records a Unknown severity vulnerability in xsk: Fix race condition in AF_XDP generic RX path. 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 | >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <975b372313dc018b9bd6cc0d85d188787054b19e || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <b6978c565ce33658543c637060852434b4248d30 || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <65d3c570614b892257dc58a1b202908242ecf8fd || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <75a240a3e8abf17b9e00b0ef0492b1bbaa932251 || >=bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 <a1356ac7749cafc4e27aa62c0c4604b5dca4983e || fd7c22ba7a0ad898b9ecf77dd53f5ccc48492e35 || 8a090e3b73eaffe18e08ccc3fb5abecf6b0a9781 || >=5.1.20 <5.2 || >=5.2.3 <5.3 | 975b372313dc018b9bd6cc0d85d188787054b19e, b6978c565ce33658543c637060852434b4248d30, 65d3c570614b892257dc58a1b202908242ecf8fd, 75a240a3e8abf17b9e00b0ef0492b1bbaa932251, a1356ac7749cafc4e27aa62c0c4604b5dca4983e, 5.2, 5.3 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
May 20, 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: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp socket from all maps and waits for completion of all outstanding rx operations. Packets in RX path will either complete safely or drop.
Quoted source text, attributed separately from HOL analysis.