CVE-2025-39969
Last modified
CVE-2025-39969 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: i40e: fix validation of VF state in get resources VF state I40E_VF_STATE_ACTIVE is not the only state in which VF is actually active so it should not be used to determine if a VF is allowed to obtain resources. Use I40E_VF_STATE_RESOURCES_LOADED that is set only in i40e_vc_get_vf_resources_msg() and cleared during reset.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: i40e: fix validation of VF state in get resources VF state I40E_VF_STATE_ACTIVE is not the only state in which VF is actually active so it should not be used to determine if a VF is allowed to obtain resources. Use I40E_VF_STATE_RESOURCES_LOADED that is set only in i40e_vc_get_vf_resources_msg() and cleared during reset.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 171527da84149c2c7aa6a60a64b09d24f3546298, < 185745d56ec958bf8aa773828213237dfcc32f5a; >= eb87117c27e729b0aeef4d72ed40d6a1761b0f68, < f47876788a23de296c42ef9d505b5c1630f0b4b8; >= 2132643b956f553f5abddc9bae20dae267b082e0, < 8e35c80f8570426fe0f0cc92b151ebd835975f22; >= 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516, < 6c3981fd59ef11a75005ac9978f034da5a168b6a; >= 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516, < e748f1ee493f88e38b77363a60499f979d42c58a; >= 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516, < 6128bbc7adc25c87c2f64b5eb66a280b78ef7ab7; >= 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516, < a991dc56d3e9a2c3db87d0c3f03c24f6595400f1; >= 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516, < 877b7e6ffc23766448236e8732254534c518ba42; >= 5.4.165, < 5.4.300; >= 5.10.85, < 5.10.245; >= 5.15.8, < 5.15.194 |
| Linux | Linux | 5.16 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-39969?
How severe is CVE-2025-39969?
How do I fix CVE-2025-39969?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39963In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39964In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2025-39965In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39966In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-39967In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39968In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2025-3997A vulnerability classified as problematic has been found in …5.3
- CVE-2025-39970In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2025-39971In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2025-39972In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2025-39973In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2025-39974In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-39969?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST