# CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered

> A race condition in the Linux kernel SATA driver can cause a spurious interrupt storm if initialization fails, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68395, DEBIAN-CVE-2026-68395, GHSA-958q-f6w8-qqgc, UBUNTU-CVE-2026-68395

## What is CVE-2026-68395?

CVE-2026-68395 is a denial of service vulnerability in Linux, published on 10 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:

ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered

sata_dwc_enable_interrupts() is called before platform_get_irq() and
ata_host_activate(), leaving the SATA controller's interrupt mask
enabled without a registered handler.  If a later step fails (irq
request, phy init, etc.) or if the controller asserts an interrupt
during probe, the irq line may fire with no handler, causing a
spurious interrupt storm.

Move sata_dwc_enable_interrupts() after ata_host_activate() so that
interrupts are only unmasked once the handler is registered and the
core is fully initialized.

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


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

Apply the vendor's patch.

## Is CVE-2026-68395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68395 is a denial of service vulnerability in Linux, published on 10 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-68395 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-68395/ (Markdown: https://insights.sbomify.com/CVE-2026-68395/index.md)
```

## Sources

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

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