Menu

Star on GitHub · 3.3k

CVE-2025-38413

7.7 · HIGH

In the Linux kernel, the following vulnerability has been resolved: virtio-net: xsk: rx: fix the frame's length check When calling buf_to_xdp, the len argument is the frame data's length without…

Published Jul 25, 2025EPSS 0.18%

Overview

CVE-2025-38413 is a high-severity vulnerability. It was published on July 25, 2025 and has a CVSS 3.1 base score of 7.7 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.7, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

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

virtio-net: xsk: rx: fix the frame's length check

When calling buf_to_xdp, the len argument is the frame data's length

without virtio header's length (vi->hdr_len). We check that len with

xsk_pool_get_rx_frame_size() + vi->hdr_len

to ensure the provided len does not larger than the allocated chunk

size. The additional vi->hdr_len is because in virtnet_add_recvbuf_xsk,

we use part of XDP_PACKET_HEADROOM for virtio header and ask the vhost

to start placing data from

hard_start + XDP_PACKET_HEADROOM - vi->hdr_len

not

hard_start + XDP_PACKET_HEADROOM

But the first buffer has virtio_header, so the maximum frame's length in

the first buffer can only be

xsk_pool_get_rx_frame_size()

not

xsk_pool_get_rx_frame_size() + vi->hdr_len

like in the current check.

This commit adds an additional argument to buf_to_xdp differentiate

between the first buffer and other ones to correctly calculate the maximum

frame's length.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-38413?

CVE-2025-38413 is a high-severity vulnerability. It was published on July 25, 2025 and has a CVSS 3.1 base score of 7.7 (HIGH).

How severe is CVE-2025-38413?

This vulnerability has a CVSS 3.1 base score of 7.7, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2025-38413?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38413?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38413 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all