CVE-2025-37912: ice: Check VF VSI Pointer Value in ice_vc_add_fdir_fltr()
In the Linux kernel, the following vulnerability has been resolved:
ice: Check VF VSI Pointer Value in ice_vc_add_fdir_fltr()
As mentioned in the commit baeb705fd6a7 ("ice: always check VF VSI
pointer values"), we need to perform a null pointer check on the return
value of ice_get_vf_vsi() before using it.
Security readout for executives and security teams
Plain-English summary
CVE-2025-37912 is a Linux kernel flaw in the Intel ice network driver. The fix adds a missing null-pointer check before using a VF VSI pointer. The public record does not provide a CVSS score, CWE, impact statement, or evidence of active exploitation.
Executive priority
Treat this as a routine but real kernel maintenance item unless your environment heavily uses ice-based network virtualization. There is no active-exploitation evidence in the supplied sources, but kernel driver faults can affect service reliability on exposed infrastructure.
Technical view
The issue is in ice_vc_add_fdir_fltr(), where ice_get_vf_vsi() could return null and the code used the result without validation. Kernel stable commits add the required check, consistent with prior guidance to always validate VF VSI pointer values.
Likely exposure
Exposure appears limited to Linux systems using affected kernel builds with the ice driver code path, likely involving virtual functions and Flow Director filter handling. The provided data lists affected and unaffected kernel versions and commits, but does not define all distributions or runtime prerequisites.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of exploitation in the wild. It also does not describe a remote attack path, privileges required, or reproducible exploit conditions, so exploitation context remains incomplete.
Researcher notes
Key evidence is a Linux kernel stable fix for a missing null check in ice_vc_add_fdir_fltr(). The bundle lacks CVSS, CWE, crash impact, exploitability details, and complete distribution mapping. Validation should focus on kernel provenance and driver usage.
Mitigation direction
Review vendor kernel advisories for your distribution and kernel branch.
Apply kernel updates containing the referenced stable fixes.
Prioritize hosts using Intel ice networking with SR-IOV or VF features.
Use distribution packages rather than backporting manually where possible.
Track Debian LTS guidance if managing Debian LTS systems.
Validation and detection
Inventory running kernel versions across affected Linux hosts.
Check whether the ice driver is present and used on production systems.
Compare installed kernel builds against vendor fixed versions and referenced commits.
Review package changelogs for CVE-2025-37912 or the ice fix title.
Confirm updated hosts rebooted into the remediated kernel.
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-37912 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.
0CVSS vectors
3Timeline events
1ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 20, 2025, 15:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.