# CVE-2026-98304: net: bcmgenet: restore the hardware filters on open

> A flaw in the Linux kernel's bcmgenet driver causes network flow filters to be lost on interface restart, potentially bypassing security controls.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106386, BELL-CVE-2026-98304, DEBIAN-CVE-2026-98304, GHSA-3cc5-5jg6-g6px, UBUNTU-CVE-2026-98304

## What is CVE-2026-98304?

CVE-2026-98304 is a missing authorization vulnerability in Linux, published on 6 Oct 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:

net: bcmgenet: restore the hardware filters on open

bcmgenet_hfb_init() runs INIT_LIST_HEAD() on priv->rxnfc_list, which drops
every rule off the list, and bcmgenet_open() calls it on each ifup. Every
rule the user configured is silently lost:

  # ethtool -N eth0 flow-type ether dst $MAC action 0
  Added rule with ID 0
  # ethtool -n eth0 | grep -c Filter:
  1
  # ip link set eth0 down && ip link set eth0 up
  # ethtool -n eth0 | grep -c Filter:
  0

Initialise the lists once at probe and restore the rules on open, as
bcmgenet_resume() already does.

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


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

Apply the vendor's patch.

## Is CVE-2026-98304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98304 is a missing authorization vulnerability in Linux, published on 6 Oct 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-98304 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-98304/ (Markdown: https://insights.sbomify.com/CVE-2026-98304/index.md)
```

## Sources

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

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