# CVE-2026-98105: net: ethernet: oa_tc6: Improve the error recovery

> A flaw in the Linux kernel oa_tc6 ethernet driver allows remote attackers to cause a denial of service via buffer overflow errors during traffic oversubscription.

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98105, DEBIAN-CVE-2026-98105, GHSA-f226-mgwm-5x89, UBUNTU-CVE-2026-98105

## What is CVE-2026-98105?

CVE-2026-98105 is a denial of service 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:

net: ethernet: oa_tc6: Improve the error recovery

When oversubscribed traffic causes lot of buffer overflow errors,
probably due to loss of data chunks, driver fails to find a
data chunk with end_valid bit set, before it runs out of sk buffer
space. As a result, assert is seen during skb_put.

Now, check is made if skb buffer has enough tailroom for the
incoming data before accepting. If there is no room, current
frame is abandoned and it will start looking for a data chunk
with start_valid bit, that is a new frame.

SK buffer allocation error is considered as recoverable error.

rx_buf_overflow flag is too specific and no longer the only
condition this flag is used for. Therefore it is renamed as
wait_until_start_valid. This is more appropriate as this flag
is used to look for the next data chunk with SV bit set, after
failures like buffer overflow, buffer allocation failure, skb pointer
validity besides buffer overflow error.

Not writing to status0 if it reads 0.

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


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

Apply the vendor's patch.

## Is CVE-2026-98105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98105 is a denial of service 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-98105 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-98105/ (Markdown: https://insights.sbomify.com/CVE-2026-98105/index.md)
```

## Sources

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

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