# CVE-2026-98275: net: ethernet: cortina: Ack RX overrun interrupt correctly

> Incorrect interrupt acknowledgment in the Cortina Ethernet driver can cause denial of service by failing to clear RX overrun conditions.

- **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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106344, BELL-CVE-2026-98275, DEBIAN-CVE-2026-98275, GHSA-pxvw-xq3p-q24h, UBUNTU-CVE-2026-98275

## What is CVE-2026-98275?

CVE-2026-98275 is a denial of service 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: ethernet: cortina: Ack RX overrun interrupt correctly

The RX overrun interrupt is reported in interrupt status register 4, but
gmac_irq() acknowledges it using the RX descriptor error bit from status
register 0. For GMAC0 this writes the GMAC1 overrun bit, while for GMAC1
the shift leaves no bit in the 32-bit register.

Acknowledge the same per-port RX overrun bit that was detected.

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


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

Apply the vendor's patch.

## Is CVE-2026-98275 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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