CVE-2026-99447: spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout

If a DMA-mapped transfer times out waiting for DMATERM and neither DMA abort interrupt arrived, pci1xxxxspitransferwithdma() returns through the error label while both DMA engines are still enabled, the done/abort interrupt status is still armed and the transfer state (p->xfer, p->txsgl, p->rxsgl) is still registered.

The ISRs keep firing afterwards: they reprogram the DMA engines from p->txsgl / p->rxsgl and signal completion through p->xfer and p->spixferdone, all of which the SPI core is free to unmap or reuse once transferone() has returned, which is a use-after-free. A late done interrupt can also start the next transfer queued behind the failed one.

Stop both DMA engines, drain the pending done/abort interrupt status and synchronize the DMA IRQs before dropping the in-progress state and the transfer pointers, and re-enable the engines afterwards so that subsequent transfers keep working. The engines are only turned back on once both were confirmed to have stopped: re-enabling an engine that failed to stop would cancel the pending stop request and let it keep running into buffers the SPI core is about to unmap or free, which is exactly the window this patch closes. An engine that failed to stop is left disabled, as the abort paths already do.

The DMA interrupt status and mask registers are shared between the two SPI instances, so the cleanup drains only this instance's done/abort status bits instead of masking the interrupt lines, which would also suppress the peer instance's completion interrupts.

Also make the DMA ISRs ignore interrupts while no transfer is in progress so that a stray MSI after the cleanup can no longer act on the cleared state.

No PCI1XXXX hardware was available for testing and QEMU has no model of this PCIe part, so the timeout path was exercised with a userspace replica of the timeout branch and the DMA ISRs, with the register and interrupt accesses mocked: on the unfixed code both a wedged engine that clears after the timeout and a late done interrupt touch the freed transfer state, while with this fix applied neither does and an engine that failed to stop is left disabled. The module was also loaded and unloaded in a QEMU x8664 guest running a kernel with this fix applied.

Affected Software

2 affected componentsFixes available
linux/kernel>=6.9.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  3. Compensating control

    In spi-pci1xxxx, on DMA transfer timeout stop both DMA engines, drain this instance’s pending done/abort interrupt status, and synchronize the DMA IRQs before clearing the in-progress state or releasing transfer pointers. Make the DMA ISRs ignore interrupts when no transfer is in progress. Re-enable the engines only after both are confirmed stopped; leave any engine that failed to stop disabled.

Event History

Nov 19, 2026
CVE Published
via MITRE·02:41 PM
Data Sourced
via MITRE·02:41 PM
Description
Data Sourced
via OSV·02:41 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203