CVE-2025-37920: xsk: Fix race condition in AF_XDP generic RX path

Published May 20, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

xsk: Fix race condition in AFXDP generic RX path

Move rxlock from xsksocket to xskbuffpool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xskbuffpool.

RX queue is exclusive to xsksocket, 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 xskbuffpool.

Lock contention may be minimized in the future by some per-thread FQ buffering.

It's safe and necessary to move spinlockbh(rxlock) after xskrcvcheck(): xs->pool and spinlockinit is synchronized by xskbind() -> xskisbound() memory barriers. xskrcvcheck() may return true at the moment of xskrelease() or xskunbinddev(), however this will not cause any data races or race conditions. xskunbinddev() 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.

Affected Software

16 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.104.2-4
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.117.1-1
Microsoft azl3 kernel 6.6.96.2-1
Microsoft azl3 kernel 6.6.112.1-2
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.119.3-1
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
Linux Linux kernel=6.15-rc2
Linux Linux kernel=6.15-rc3
Linux Linux kernel=6.15-rc4
Microsoft azl3 kernel 6.6.121.1-1<6.6.126.1-1
6.6.126.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.126.1-1

Event History

May 20, 2025
CVE Published
via MITRE·03:21 PM
Data Sourced
via MITRE·03:21 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 3, 2025
Data Sourced
via Microsoft·11:01 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·11:01 PM
Affected Software
Updated
via Microsoft·11:01 PM
SeverityAffected Software
Sep 4, 2025
Updated
via Microsoft·06:01 AM
DescriptionSeverityWeakness
Updated
via Microsoft·06:01 AM
WeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-37920?

The severity of CVE-2025-37920 is classified as medium due to its potential impact on system stability and performance.

2

How do I fix CVE-2025-37920?

To fix CVE-2025-37920, update your Linux kernel to the latest version where the vulnerability has been patched.

3

What component is affected by CVE-2025-37920?

CVE-2025-37920 affects the AF_XDP implementation in the Linux kernel that handles the generic RX path.

4

Can CVE-2025-37920 be exploited remotely?

CVE-2025-37920 requires local access to the system, making remote exploitation unlikely.

5

What are the symptoms of CVE-2025-37920?

Symptoms of CVE-2025-37920 may include performance degradation or instability when using multiple sockets sharing an xsk_buff_pool.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203