CVE-2025-68766: irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 09efe7cfbf919c4d763bc425473fcfee0dc98356, 324c60a67c4b9668497940f667db14d216cc7b1b, 3873afcb57614c1aaa5b6715554d6d1c22cac95a; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 09efe7cfbf919c4d763bc425473fcfee0dc98356, 324c60a67c4b9668497940f667db14d216cc7b1b, 3873afcb57614c1aaa5b6715554d6d1c22cac95a; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 5, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.16affected
- 00fa3461c86dd289b441d4d5a6bb236064bd207b and later · before 324c60a67c4b9668497940f667db14d216cc7b1baffected · git
- 00fa3461c86dd289b441d4d5a6bb236064bd207b and later · before c21c606ad398eeb86a0f3aaff9ba4f2665e286c6affected · git
- 00fa3461c86dd289b441d4d5a6bb236064bd207b and later · before 3873afcb57614c1aaa5b6715554d6d1c22cac95aaffected · git
- 00fa3461c86dd289b441d4d5a6bb236064bd207b and later · before 09efe7cfbf919c4d763bc425473fcfee0dc98356affected · git
- 00fa3461c86dd289b441d4d5a6bb236064bd207b and later · before efd65e2e2fd96f7aaa5cb07d79bbbfcfc80aa552affected · git
- 00fa3461c86dd289b441d4d5a6bb236064bd207b and later · before 7dbc0d40d8347bd9de55c904f59ea44bcc8dedb7affected · git
- before 5.16not affected · semver
- 6.1.160 and later · up to and including 6.1.*not affected · semver
- 6.6.120 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68764Jan 5, 2026 · NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags31Monitor
- ← EarlierCVE-2025-68765Jan 5, 2026 · mt76: mt7615: Fix memory leak in mt7615_mcu_wtbl_sta_add()0Monitor
- Later →CVE-2025-68767Jan 13, 2026 · hfsplus: Verify inode mode when loading from disk0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 09efe7cfbf919c4d763bc425473fcfee0dc98356 | Vendor (CNA) |
| Linux Linux | 324c60a67c4b9668497940f667db14d216cc7b1b | Vendor (CNA) |
| Linux Linux | 3873afcb57614c1aaa5b6715554d6d1c22cac95a | Vendor (CNA) |
| Linux Linux | 7dbc0d40d8347bd9de55c904f59ea44bcc8dedb7 | Vendor (CNA) |
| Linux Linux | c21c606ad398eeb86a0f3aaff9ba4f2665e286c6 | Vendor (CNA) |
| Linux Linux | efd65e2e2fd96f7aaa5cb07d79bbbfcfc80aa552 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/324c60a67c4b9668497940f667db14d216cc7b1b
- git.kernel.org/stable/c/3873afcb57614c1aaa5b6715554d6d1c22cac95a
- git.kernel.org/stable/c/7dbc0d40d8347bd9de55c904f59ea44bcc8dedb7
- git.kernel.org/stable/c/c21c606ad398eeb86a0f3aaff9ba4f2665e286c6
- git.kernel.org/stable/c/efd65e2e2fd96f7aaa5cb07d79bbbfcfc80aa552
Vendor advisories and official records. Exploit/PoC links are deliberately left out.