# CVE-2026-98808: net: systemport: Fix buffer overflow in bcm_sysport_get_stats()

> A buffer overflow in the Linux kernel's SYSTEMPORT Lite driver allows attackers to cause memory corruption, potentially leading to code execution or system crashes.

- **Severity:** Not scored
- **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:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109074, BELL-CVE-2026-98808, DEBIAN-CVE-2026-98808, GHSA-887q-3qpv-x22r, UBUNTU-CVE-2026-98808

## What is CVE-2026-98808?

CVE-2026-98808 is a memory corruption vulnerability in Linux, published on 18 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: systemport: Fix buffer overflow in bcm_sysport_get_stats()

When running on SYSTEMPORT Lite, certain statistics are unsupported and
skipped during bcm_sysport_get_stats(). The variable 'j' tracks the
compacted index into the destination data buffer, whereas 'i' iterates
over all elements in bcm_sysport_gstrings_stats.

Because the buffer allocated by ethtool is sized only according to
bcm_sysport_get_sset_count(), storing values at data[i] instead of
data[j] writes past the allocated array bounds, leading to memory
corruption.

Fix this by writing to data[j] instead of data[i].

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


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

Apply the vendor's patch.

## Is CVE-2026-98808 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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