[CVE-2026-72425][LOW] ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() [ Upstream

[CVE-2026-72425][LOW] ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72425
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() [ Upstream
Commit: b409a9dc37db8bd798122fc5bcdcfaccaf80db1e
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b409a9dc37db8bd798122fc5bcdcfaccaf80db1e
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72425
Analysis date: Sat, 15 Aug 2026 06:45:41 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
The ice driver may leak CTRL VSI resources when all VFs are reset while VF FDIR filters are enabled, allowing a privileged local administrator-level actor to cause device resource exhaustion after repeated reset cycles.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72425 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72425

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72425	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-772;CWE-404;**CWE-400;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'The ice driver can leak CTRL VSI resources when all VFs are reset while a VF has FDIR filters enabled. The vulnerable path invalidates the CTRL VSI instead of releasing it, so repeated reset cycles may consume driver or hardware resources and eventually affect availability. For the CVSS the PR:H is used because reliable triggering requires administrative control over SR IOV VF setup, ethtool FDIR filter programming, and PF device reset on the host. The issue is not directly network reachable and is triggered through local device management operations rather than packet traffic. Impact is resource exhaustion and denial of service only. No memory corruption primitive, information leak, or privilege escalation path is indicated by the changed code.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	REMOTE SIMPLEFIX LEAK NETWORK  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

* Availability impact realistic: +1 paranoid only. Repeated PF reset cycles with VF FDIR filters may leak CTRL VSI resources and eventually cause device or driver resource exhaustion.
* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2. The reproducer requires SR-IOV VF setup, ethtool FDIR rule programming, and PF device reset through sysfs.
* Rare and hardware/configuration dependent path: -1. The issue requires Intel ice hardware, SR-IOV VFs, FDIR filters, and reset-all-VFs behavior.
* No memory corruption signal: +0. The patch changes invalidate to release and indicates a resource leak, not UAF, OOB write, double free, type confusion, or attacker-controlled overwrite.
* No privilege escalation plausible: +0. No supported path to LPE, information disclosure, or integrity impact is visible.
* No remote/network-triggerable exposure: +0. Packet traffic alone is not shown to trigger the bug.

## 3. Reachability analysis

The reliable trigger is local administrative device management on the host. A typical attacker needs control over SR-IOV configuration, VF FDIR filter setup, and PF reset operations. Namespaces or containers do not normally lower this to unprivileged access unless the environment explicitly delegates PF or SR-IOV administration to tenants. The affected path is not default-exposed to remote network attackers and depends on specific Intel ice NIC functionality and runtime configuration.

## 4. Severity interpretation

This behaves like a low-end resource leak / DoS issue rather than an Important-class kernel vulnerability. The realistic impact is exhaustion of driver or hardware VSI resources after repeated privileged reset cycles. Theoretical impact remains availability-only because the patch and context do not support memory corruption, file or credential exposure, or privilege escalation.

## 5. One-sentence report phrase

The ice driver may leak CTRL VSI resources when all VFs are reset while VF FDIR filters are enabled, allowing a privileged local administrator-level actor to cause device resource exhaustion after repeated reset cycles.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED.

This can be auto-closed for urgent triage purposes because it is a privileged, hardware-specific resource leak with no demonstrated memory corruption, confidentiality impact, integrity impact, or privilege escalation path.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() [ Upstream
Commit: b409a9dc37db8bd798122fc5bcdcfaccaf80db1e
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b409a9dc37db8bd798122fc5bcdcfaccaf80db1e

Changed files:
  drivers/net/ethernet/intel/ice/ice_vf_lib.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b409a9dc37db8bd798122fc5bcdcfaccaf80db1e

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72425 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72425

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.4

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).