# CVE-2026-93814: spi: core: Abort active target transfer on controller suspend

> A flaw in the Linux kernel SPI subsystem can cause system hangs during suspend if an active target transfer is not aborted, requiring a kernel patch.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103817, BELL-CVE-2026-93814, DEBIAN-CVE-2026-93814, GHSA-5c56-qrwc-9499, UBUNTU-CVE-2026-93814

## What is CVE-2026-93814?

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

spi: core: Abort active target transfer on controller suspend

When an SPI controller operating in target mode has a transfer in
progress at the time of system suspend, the suspend path proceeds
without aborting the ongoing transfer. This can leave the hardware in
an inconsistent state, potentially causing the system to hang or fail
to resume cleanly.

Fix this by invoking the controller's target_abort callback from
spi_controller_suspend() when the controller is in target mode and the
callback is registered. This ensures any active target transfer is
cleanly terminated before the controller is suspended.

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


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

Apply the vendor's patch.

## Is CVE-2026-93814 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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