# CVE-2026-90080: octeontx2-pf: fix NULL deref of af_xdp_zc_qidx on rep setup

> A local attacker with high privileges can cause a kernel crash by triggering a NULL pointer dereference in the octeontx2-pf driver during representor setup.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-90080, DEBIAN-CVE-2026-90080, GHSA-5wx6-43ww-fw3m, UBUNTU-CVE-2026-90080

## What is CVE-2026-90080?

CVE-2026-90080 is a vulnerability in Linux, published on 17 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:

octeontx2-pf: fix NULL deref of af_xdp_zc_qidx on rep setup

af_xdp_zc_qidx tracks receive queues using AF_XDP zero-copy and is
allocated during PF/VF probe. Representors and other non-AF_XDP paths
leave the pointer NULL, but several call sites used test_bit() on it
unconditionally.

Switching to devlink eswitch mode creates representors and runs
otx2_init_hw_resources(), which reaches otx2_pool_aq_init() and oopses
when dereferencing the NULL bitmap. Add NULL checks before every
af_xdp_zc_qidx test_bit() use in the RSS, ethtool, XSK, and pool init
paths.

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


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

Apply the vendor's patch.

## Is CVE-2026-90080 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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