# CVE-2026-93246: octeontx2-af: fix out-of-bounds read setting MSI-X irq affinity

> An out-of-bounds read in the octeontx2-af kernel driver can cause a crash or leak memory when debug options are enabled during boot.

- **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:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93246, GHSA-52xx-jr85-g6wq, UBUNTU-CVE-2026-93246

## What is CVE-2026-93246?

CVE-2026-93246 is a memory corruption vulnerability in Linux, published on 24 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-af: fix out-of-bounds read setting MSI-X irq affinity

rvu_register_interrupts() walks every MSI-X vector and uses strstr()
to match "Mbox" or "FLR" in irq_name before pinning those interrupts
to CPU 0. irq_name is a per-vector NAME_SIZE buffer, but not every
slot is populated before this loop runs. strstr() keeps scanning until
it finds a NUL terminator, so an uninitialized slot can trigger a KASAN
slab-out-of-bounds read at boot when debug options are enabled.

Use strnstr() with NAME_SIZE to bound the search within each vector's
name buffer.

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


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

Apply the vendor's patch.

## Is CVE-2026-93246 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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