# CVE-2026-80779: net/ionic: avoid OOB TX partner lookup for hwstamp RXQ

> An out-of-bounds memory access in the Linux kernel's ionic network driver allows attackers to potentially execute code or cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-80779, DEBIAN-CVE-2026-80779, GHSA-5565-rhhw-mpqw, UBUNTU-CVE-2026-80779

## What is CVE-2026-80779?

CVE-2026-80779 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net/ionic: avoid OOB TX partner lookup for hwstamp RXQ

The dedicated hardware timestamp RX queue is allocated with q->index
equal to lif->ionic->nrxqs_per_lif. The normal txqcqs array only
contains the regular queue pairs, so using that index to set rxq->partner
can read one entry past txqcqs[] and then write through the derived
pointer.
Only link RX/TX partners for normal queue-pair indexes. Leave the hwstamp
RX queue unpaired, and make the XDP_TX path abort cleanly if an RX queue
has no TX partner.

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


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

Apply the vendor's patch.

## Is CVE-2026-80779 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80779 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80779 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-80779/ (Markdown: https://insights.sbomify.com/CVE-2026-80779/index.md)
```

## Sources

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

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