CVE-2025-37920
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Linux Kernel < 5.2
- Linux Kernel < 6.12.28
- Linux Kernel < 6.14.6
- Linux Kernel 6.15
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-37920.md and follow it. Check whether this project is affected by CVE-2025-37920. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/65d3c570614b892257dc58a1b202908242ecf8fd
- https://git.kernel.org/stable/c/75a240a3e8abf17b9e00b0ef0492b1bbaa932251
- https://git.kernel.org/stable/c/975b372313dc018b9bd6cc0d85d188787054b19e
- https://git.kernel.org/stable/c/a1356ac7749cafc4e27aa62c0c4604b5dca4983e
- https://git.kernel.org/stable/c/b6978c565ce33658543c637060852434b4248d30
References
- https://git.kernel.org/stable/c/65d3c570614b892257dc58a1b202908242ecf8fd
- https://git.kernel.org/stable/c/75a240a3e8abf17b9e00b0ef0492b1bbaa932251
- https://git.kernel.org/stable/c/975b372313dc018b9bd6cc0d85d188787054b19e
- https://git.kernel.org/stable/c/a1356ac7749cafc4e27aa62c0c4604b5dca4983e
- https://git.kernel.org/stable/c/b6978c565ce33658543c637060852434b4248d30