# CVE-2026-23180: dpaa2-switch: add bounds check for if_id in IRQ handler

> An out-of-bounds read in the dpaa2-switch IRQ handler allows attackers to potentially disclose memory or cause a denial of service.

- **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:** 14 Feb 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-77664, BELL-CVE-2026-23180, DEBIAN-CVE-2026-23180, GHSA-pmxm-x3p3-w327, ROOT-OS-DEBIAN-12-CVE-2026-23180, ROOT-OS-DEBIAN-13-CVE-2026-23180, ROOT-OS-UBUNTU-2204-CVE-2026-23180, ROOT-OS-UBUNTU-2404-CVE-2026-23180, UBUNTU-CVE-2026-23180

## What is CVE-2026-23180?

CVE-2026-23180 is a high-severity memory corruption vulnerability in Linux, published on 14 Feb 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:

dpaa2-switch: add bounds check for if_id in IRQ handler

The IRQ handler extracts if_id from the upper 16 bits of the hardware
status register and uses it to index into ethsw->ports[] without
validation. Since if_id can be any 16-bit value (0-65535) but the ports
array is only allocated with sw_attr.num_ifs elements, this can lead to
an out-of-bounds read potentially.

Add a bounds check before accessing the array, consistent with the
existing validation in dpaa2_switch_rx().

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-23180 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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