LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause an out-of-bounds access in the mchp-eic interrupt controller code when invalid hardware interrupt data is accepted as successful. Business urgency is unclear because the source bundle provides no CVSS score, no impact rating, and no confirmed exploitation.

Executive priority

Treat as watch-and-patch unless your fleet uses affected Linux kernels on platforms with this interrupt controller path. Escalate priority only if vendor advisories identify exploitable impact in your environment.

Technical view

mchp_eic_domain_alloc() checks for hwirq values at or above MCHP_EIC_NIRQ but previously failed to set an error code. That could return success after irq_domain_translate_twocell() supplied an invalid hwirq, leading to out-of-bounds access. Stable kernel commits change the path to return -EINVAL.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the mchp-eic irqchip driver is present and reachable. The bundle does not identify specific distributions, appliances, hardware models, configurations, or CPEs.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation. The bundle does not describe a remote, local, or physical attack path, nor required privileges or practical exploitability.

Researcher notes

Evidence is narrow: the bug and fix are clear, but severity, attacker position, and affected deployment scope are not. Avoid extrapolating beyond the mchp-eic allocation path and the stable commit remediation.

Mitigation direction

  • Update to a vendor kernel containing the cited stable fix commits.
  • Track distribution or device vendor advisories for packaged kernel availability.
  • Prioritize systems that build or deploy the mchp-eic irqchip driver.
  • Document non-exposure where the driver or relevant hardware path is absent.

Validation and detection

  • Inventory Linux kernel versions against the affected version data.
  • Check kernel source or changelogs for the cited stable commit hashes.
  • Confirm whether mchp-eic support is built or deployed on target systems.
  • Review vendor advisories for any distribution-specific impact or backport notes.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68766 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux00fa3461c86dd289b441d4d5a6bb236064bd207b, 00fa3461c86dd289b441d4d5a6bb236064bd207b, 00fa3461c86dd289b441d4d5a6bb236064bd207b, 00fa3461c86dd289b441d4d5a6bb236064bd207b, 00fa3461c86dd289b441d4d5a6bb236064bd207b, 00fa3461c86dd289b441d4d5a6bb236064bd207bunaffected
LinuxLinux5.16, 0, 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.