CVE-2025-37920
Last modified
CVE-2025-37920 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.1.20, < 5.2 | — |
| Linux | Linux Kernel | >= 5.2.3, < 6.12.28 | — |
| Linux | Linux Kernel | >= 6.13, < 6.14.6 | — |
| Linux | Linux Kernel | 6.15 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-37920?
How severe is CVE-2025-37920?
How do I fix CVE-2025-37920?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-37915In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-37916In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37917In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37918In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37919In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3792A vulnerability, which was classified as critical, has been …7.2
- CVE-2025-37921In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37922In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37923In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37924In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37925In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37926In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-37920?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
