# CVE-2026-98028: eth: nfp: drop the replaced rule from the list when reprogramming fails

> A logic error in the Linux kernel NFP driver causes a buffer overflow when reprogramming fails, allowing local attackers to cause denial of service or read memory.

- **Severity:** Not scored
- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98028, DEBIAN-CVE-2026-98028, GHSA-9537-hf5q-v67h, UBUNTU-CVE-2026-98028

## What is CVE-2026-98028?

CVE-2026-98028 is a memory corruption vulnerability in Linux, published on 25 Sep 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:

eth: nfp: drop the replaced rule from the list when reprogramming fails

nfp_net_fs_add() replaces an existing rule by deleting it from the
hardware, decrementing nn->fs.count and programming the new one.  If
nfp_net_fs_add_hw() fails the old entry stays on nn->fs.list - only the
success path reaches list_replace() - so the list is one longer than
nn->fs.count, and it advertises a rule whose hardware entry has already
been torn down.

nn->fs.count is what ETHTOOL_GRXCLSRLCNT reports, so userspace then sizes
its buffer one entry short of what the GRXCLSRLALL walk wants to write.
That used to overwrite one u32 past the allocation; since the walk is
bounded it is a permanent -EMSGSIZE instead, as nothing ever resyncs the
counter.

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


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

Apply the vendor's patch.

## Is CVE-2026-98028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98028 is a memory corruption vulnerability in Linux, published on 25 Sep 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-98028 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-98028/ (Markdown: https://insights.sbomify.com/CVE-2026-98028/index.md)
```

## Sources

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

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