# CVE-2025-68766: irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc()

> A missing error check in the Linux kernel Microchip EIC driver allows out-of-bounds access, potentially causing a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2026
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68766, DEBIAN-CVE-2025-68766, GHSA-8866-wmp5-q7xv, ROOT-OS-DEBIAN-12-CVE-2025-68766, ROOT-OS-DEBIAN-13-CVE-2025-68766, ROOT-OS-UBUNTU-2404-CVE-2025-68766, UBUNTU-CVE-2025-68766

## What is CVE-2025-68766?

CVE-2025-68766 is a vulnerability in Linux, published on 5 Jan 2026. 

### Official description

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

irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc()

If irq_domain_translate_twocell() sets "hwirq" to >= MCHP_EIC_NIRQ (2) then
it results in an out of bounds access.

The code checks for invalid values, but doesn't set the error code.  Return
-EINVAL in that case, instead of returning success.

## Which versions are affected by CVE-2025-68766?


## How do I fix CVE-2025-68766?

Apply the vendor's patch.

## Is CVE-2025-68766 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68766 and fix it if it is affected.

What it is: CVE-2025-68766 is a vulnerability in Linux, published on 5 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-68766 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-2025-68766/ (Markdown: https://insights.sbomify.com/CVE-2025-68766/index.md)
```

## Sources

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

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