# CVE-2026-64587: net: ethernet: arc: emac: quiesce interrupts before requesting IRQ

> A race condition in the ARC EMAC Ethernet driver allows stale interrupts to cause a use-after-free during probe teardown, leading to system crashes.

- **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:** 6 Aug 2026
- **Updated:** 8 Aug 2026
- **Also known as:** BELL-CVE-2026-64587, DEBIAN-CVE-2026-64587, GHSA-9p7c-hfwg-795w, UBUNTU-CVE-2026-64587

## What is CVE-2026-64587?

CVE-2026-64587 is a high-severity vulnerability in Linux, published on 6 Aug 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: ethernet: arc: emac: quiesce interrupts before requesting IRQ

Normal RX/TX interrupts are enabled later, in arc_emac_open(), so probe
should not see interrupt delivery in the usual case. However, hardware may
still present stale or latched interrupt status left by firmware or the
bootloader.

If probe later unwinds after devm_request_irq() has installed the handler,
such a stale interrupt can still reach arc_emac_intr() during teardown and
race with release of the associated net_device.

Avoid that window by putting the device into a known quiescent state before
requesting the IRQ: disable all EMAC interrupt sources and clear any
pending EMAC interrupt status bits. This keeps the change hardware-focused
and minimal, while preventing spurious IRQ delivery from leftover state.

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


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

Apply the vendor's patch.

## Is CVE-2026-64587 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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