CVE-2025-37920xsk: Fix race condition in AF_XDP generic RX path
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 34 days later
· 34 days later
Published
- 17 months later
· 17 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 – < 975b372313dc018b9bd6cc0d85d188787054b19e
- affected bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 – < b6978c565ce33658543c637060852434b4248d30
- affected bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 – < 65d3c570614b892257dc58a1b202908242ecf8fd
- affected bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 – < 75a240a3e8abf17b9e00b0ef0492b1bbaa932251
- affected bf0bdd1343efbbf65b4d53aef1fce14acbd79d50 – < a1356ac7749cafc4e27aa62c0c4604b5dca4983e
- affected fd7c22ba7a0ad898b9ecf77dd53f5ccc48492e35
- affected 8a090e3b73eaffe18e08ccc3fb5abecf6b0a9781
- affected 5.1.20 – < 5.2
- affected 5.2.3 – < 5.3
- affected 5.3
- unaffected < 5.3
- unaffected 6.1.164 – ≤ 6.1.*
- unaffected 6.6.123 – ≤ 6.6.*
- unaffected 6.12.28 – ≤ 6.12.*
- unaffected 6.14.6 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References5
- https://git.kernel.org/stable/c/975b372313dc018b9bd6cc0d85d188787054b19e (opens in a new tab)
- https://git.kernel.org/stable/c/b6978c565ce33658543c637060852434b4248d30 (opens in a new tab)
- https://git.kernel.org/stable/c/65d3c570614b892257dc58a1b202908242ecf8fd (opens in a new tab)
- https://git.kernel.org/stable/c/75a240a3e8abf17b9e00b0ef0492b1bbaa932251 (opens in a new tab)
- https://git.kernel.org/stable/c/a1356ac7749cafc4e27aa62c0c4604b5dca4983e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-15945 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-37920)Record last updated .