# CVE-2023-54040: ice: fix wrong fallback logic for FDIR

> A logic error in the Intel ice network driver causes memory leaks and inconsistent states during filter failures, potentially leading to denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-54040, DEBIAN-CVE-2023-54040, GHSA-jp7h-x2g7-335v, UBUNTU-CVE-2023-54040

## What is CVE-2023-54040?

CVE-2023-54040 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. 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 wrong fallback logic for FDIR

When adding a FDIR filter, if ice_vc_fdir_set_irq_ctx returns failure,
the inserted fdir entry will not be removed and if ice_vc_fdir_write_fltr
returns failure, the fdir context info for irq handler will not be cleared
which may lead to inconsistent or memory leak issue. This patch refines
failure cases to resolve this issue.

## Which versions are affected by CVE-2023-54040?


## How do I fix CVE-2023-54040?

Apply the vendor's patch.

## Is CVE-2023-54040 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54040 and fix it if it is affected.

What it is: CVE-2023-54040 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. 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-2023-54040 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-2023-54040/ (Markdown: https://insights.sbomify.com/CVE-2023-54040/index.md)
```

## Sources

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

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