# CVE-2026-23013: net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback

> A use-after-free vulnerability in the Linux kernel's octeon_ep_vf driver allows attackers to cause a crash or potentially execute code via improper IRQ rollback handling.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jan 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-23013, DEBIAN-CVE-2026-23013, GHSA-r5qx-544g-4q99, ROOT-OS-DEBIAN-13-CVE-2026-23013, UBUNTU-CVE-2026-23013

## What is CVE-2026-23013?

CVE-2026-23013 is a high-severity use after free vulnerability in Linux kernel, published on 25 Jan 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: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback

octep_vf_request_irqs() requests MSI-X queue IRQs with dev_id set to
ioq_vector. If request_irq() fails part-way, the rollback loop calls
free_irq() with dev_id set to 'oct', which does not match the original
dev_id and may leave the irqaction registered.

This can keep IRQ handlers alive while ioq_vector is later freed during
unwind/teardown, leading to a use-after-free or crash when an interrupt
fires.

Fix the error path to free IRQs with the same ioq_vector dev_id used
during request_irq().

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-23013 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23013 is a high-severity use after free vulnerability in Linux kernel, published on 25 Jan 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-23013 in the wild and no public exploit code.

Affected product: Linux kernel. 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-23013/ (Markdown: https://insights.sbomify.com/CVE-2026-23013/index.md)
```

## Sources

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

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