CVE-2025-39968: i40e: add max boundary check for VF filters
In the Linux kernel, the following vulnerability has been resolved:
i40e: add max boundary check for VF filters
There is no check for max filters that VF can request. Add it.
Security readout for executives and security teams
Plain-English summary
A locally authorized Linux virtual function may request too many network filters from the i40e driver because the driver lacked a maximum-boundary check. The supplied CVSS assessment indicates possible major availability impact and limited integrity impact, but no confidentiality loss. Risk is concentrated on affected systems using i40e virtual-function filtering, rather than every Linux installation.
Executive priority
Treat this as a high-priority infrastructure issue where i40e virtual functions cross trust boundaries or support critical services. Schedule vendor-supported kernel remediation promptly. Lower the priority only after confirming the vulnerable path is unused or inaccessible; the evidence does not support an emergency internet-wide response.
Technical view
CVE-2025-39968 is an input-boundary flaw in the Linux kernel i40e driver's handling of virtual-function filter requests. The resolution adds a maximum filter check. CVSS 3.1 is 7.3: local access, low complexity, low privileges, no user interaction, changed scope, low integrity impact, and high availability impact.
Likely exposure
Prioritize Linux hosts running affected kernel code where i40e virtual functions can submit filter requests, particularly environments assigning such functions to less-trusted workloads. Hosts not using the relevant i40e virtual-function functionality are less likely to expose the vulnerable path. The supplied version data is ambiguous, so confirm applicability through the kernel or distribution vendor.
Exploitation context
Exploitation requires local, low-privileged access according to the supplied CVSS vector; this is not described as a remote network attack. The bundle marks the CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Absence from KEV does not prove exploitation is impossible.
Researcher notes
The record supplies only a short root-cause statement: no maximum check existed for filters requested by a virtual function. It does not identify a CWE, failure mode, affected hardware models, exploit proof, or precise fixed release mapping. Validate backports using the referenced stable commits and vendor advisories rather than version-string assumptions.
Mitigation direction
Obtain a kernel update incorporating the applicable listed stable fix from your Linux distribution or kernel vendor.
Prioritize hosts exposing i40e virtual functions to tenants, containers, virtual machines, or other less-trusted workloads.
If updating is delayed, consult vendor guidance about safely restricting the affected virtual-function functionality.
Do not infer fixed versions solely from the ambiguous version list in the supplied record.
Validation and detection
Inventory kernel versions, i40e driver use, SR-IOV configuration, and assigned virtual functions across Linux hosts.
Confirm the installed kernel contains the applicable stable commit or vendor backport.
Identify which users or workloads can control i40e virtual functions and request filters.
After updating, verify the running kernel package and confirm normal virtual-function networking behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-39968 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.