CVE-2025-39969 — i40e: fix validation of VF state in get resources
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 171527da84149c2c7aa6a60a64b09d24f3546298 and < 185745d56ec958bf8aa773828213237dfcc32f5a≥ eb87117c27e729b0aeef4d72ed40d6a1761b0f68 and < f47876788a23de296c42ef9d505b5c1630f0b4b8≥ 2132643b956f553f5abddc9bae20dae267b082e0 and < 8e35c80f8570426fe0f0cc92b151ebd835975f22≥ 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516 and < 6c3981fd59ef11a75005ac9978f034da5a168b6a≥ 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516 and < e748f1ee493f88e38b77363a60499f979d42c58a≥ 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516 and < 6128bbc7adc25c87c2f64b5eb66a280b78ef7ab7≥ 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516 and < a991dc56d3e9a2c3db87d0c3f03c24f6595400f1≥ 61125b8be85dfbc7e9c7fe1cc6c6d631ab603516 and < 877b7e6ffc23766448236e8732254534c518ba42 and 4 more≥ 5.4.165 and < 5.4.300≥ 5.10.85 and < 5.10.245≥ 5.15.8 and < 5.15.194version 5.16 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.0 | 6.0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.15%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · linux/linux
- Record published
- CVSS changed · 8.8
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
10 on the record
- git.kernel.org/stable/c/6c3981fd59ef11a75005ac9978f034da5a168b6a
- git.kernel.org/stable/c/185745d56ec958bf8aa773828213237dfcc32f5a
- git.kernel.org/stable/c/6128bbc7adc25c87c2f64b5eb66a280b78ef7ab7
- git.kernel.org/stable/c/a991dc56d3e9a2c3db87d0c3f03c24f6595400f1
- github.com/advisories/GHSA-xxpg-m5qg-jjxh
- git.kernel.org/stable/c/8e35c80f8570426fe0f0cc92b151ebd835975f22
- nvd.nist.gov/vuln/detail/CVE-2025-39969
- git.kernel.org/stable/c/e748f1ee493f88e38b77363a60499f979d42c58a
- git.kernel.org/stable/c/f47876788a23de296c42ef9d505b5c1630f0b4b8
- git.kernel.org/stable/c/877b7e6ffc23766448236e8732254534c518ba42
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-39969 is "i40e: fix validation of VF state in get resources", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.15% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.