CVE-2025-38375
Description
From CVE.org
In the Linux kernel, the following vulnerability has been resolved: virtio-net: ensure the received length does not exceed allocated size In xdp_linearize_page, when reading the following buffers from the ring, we forget to check the received length with the true allocate size. This can lead to an out-of-bound read. This commit adds that missing check.
Statement
This vulnerability arises from missing bounds checks in xdp_linearize_page(), which can lead to an out-of-bounds read if the virtio-backend provides an invalid buffer length. The issue can be triggered by a malicious or compromised host/hypervisor that controls the virtqueue, resulting in memory disclosure or denial-of-service within the guest kernel.
The CVSS vector uses AV:A (Adjacent Network) rather than AV:N, because the attack requires control of the local virtio communication channel between host and guest rather than being launched over an arbitrary external network. This reflects that the threat originates from an adjacent execution environment (e.g., host, co-tenant, or hypervisor component) rather than a remote Internet attacker.
The issue is rated PR:H because only privileged control of the virtio-net device (e.g., by the hypervisor or a privileged host process) can supply crafted buffers to reach the flawed code path, making it inaccessible to unprivileged guest users or remote attackers.
Mitigation
To mitigate this issue, prevent module virtio_net from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.2 | 7.8 | 8.4 |
| Attack Vector | Adjacent Network | Local | Local |
| Attack Complexity | Low | Low | Low |
| Privileges Required | High | Low | None |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | Low | High | High |
| Integrity Impact | None | High | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
