CVE-2025-39973
In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The parameter provided by the virtual function (VF) is assi…
Published Oct 15, 2025 · updated Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introduce an upper boundary check for both Tx and Rx queue lengths. The maximum number of descriptors supported by the hardware is 8k-32. Additionally, enforce alignment constraints: Tx rings must be a multiple of 8, and Rx rings must be a multiple of 32.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2025 · NIST NVD
Detected
In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introduce an upper boundary check for both Tx and Rx queue lengths. The maximum number of descriptors supported by the hardware is 8k-32. Add
Oct 15, 2026 · NIST NVD
Updated
In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introduce an upper boundary check for both Tx and Rx queue lengths. The maximum number of descriptors supported by the hardware is 8k-32. Add
Sources
- CVE.orgVulnerability recordCVE-2025-39973
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2025-39973
In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introdu
nvd.nist.gov