You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
shared umem
About this tag
The shared umem tag on WindowsForum.com covers discussions about the Linux kernel's shared UMEM (User Memory) feature, particularly in the context of AF_XDP sockets. A recent thread details CVE-2025-37920, a race condition in the AF_XDP receive path where multiple sockets sharing a single UMEM could cause corrupted RX processing, dropped packets, or kernel instability. The fix moves a spinlock to the shared UMEM pool to synchronize access. This topic is relevant for administrators managing mixed Windows-Linux environments, cloud infrastructure, or container systems that rely on high-performance packet processing with shared memory. The tag focuses on kernel-level synchronization, security vulnerabilities, and operational impacts of shared UMEM configurations.
A subtle synchronization bug in the Linux kernel’s AF_XDP (XSK) receive path has been fixed upstream — the change moves a spinlock from the per-socket structure into the shared UMEM pool to eliminate a race between RX and FILL processing when multiple sockets share a single umem. This...