# CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs()

> A resource leak in the Intel ice driver during VF reset can lead to denial of service when FDIR filters are enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-72425, DEBIAN-CVE-2026-72425, GHSA-cwxj-gwrv-324j, UBUNTU-CVE-2026-72425

## What is CVE-2026-72425?

CVE-2026-72425 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs()

Resetting all VFs causes resource leak on VFs with FDIR filters
enabled as CTRL VSIs are only invalidated and not freed. Fix by using
ice_vf_ctrl_vsi_release() instead of ice_vf_ctrl_invalidate_vsi() which
aligns behavior with the ice_reset_vf() function.

Reproduction:
  echo 1 > /sys/class/net/$pf/device/sriov_numvfs
  ethtool -N $vf flow-type ether proto 0x9000 action 0
  echo 1 > /sys/class/net/$pf/device/reset

## Which versions are affected by CVE-2026-72425?


## How do I fix CVE-2026-72425?

Apply the vendor's patch.

## Is CVE-2026-72425 being exploited?

There is no known exploitation of CVE-2026-72425 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72425 and fix it if it is affected.

What it is: CVE-2026-72425 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72425 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72425/ (Markdown: https://insights.sbomify.com/CVE-2026-72425/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72425
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72425
- OSV: https://osv.dev/vulnerability/CVE-2026-72425

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72425/
Summaries are generated and may contain mistakes; the official description above is the record.