CVE-2026-93814: spi: core: Abort active target transfer on controller suspend
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 targetabort callback from spicontrollersuspend() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In spi_controller_suspend(), invoke the controller's target_abort callback when the SPI controller is in target mode and the callback is registered, so any active target transfer is terminated before suspension.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue affects Linux kernel systems using an SPI controller in target mode when a transfer is active as the system enters suspend. The controller must also have a target_abort callback registered for the fix to terminate the transfer.
What conditions are required to trigger the failure?
An SPI target-mode transfer must still be in progress when system suspend begins. Without aborting that transfer, the controller hardware can be left inconsistent, which can cause a hang or an unsuccessful resume.
How can I tell whether this may be affecting a system?
Investigate systems that hang during suspend or fail to resume cleanly while an SPI controller is operating in target mode. The relevant condition is an active target transfer at the time suspend is initiated.