CVE-2026-31560: spi: spi-dw-dma: fix print error log when wait finish transaction

Published Apr 24, 2026
·
Updated

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

Other sources

spi: spi-dw-dma: fix print error log when wait finish transaction

— Microsoft

Affected Software

11 affected componentsFixes available
Linux SPI DesignWare DMA driver (spi-dw-dma)
Linux Linux kernel>=5.8.1<6.19.11
Linux Linux kernel=5.8
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
debian/linux<=6.1.176-1, <=6.1.187-1
6.12.107-17.2.6-17.2.7-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 6.12.107-1Fixed in 7.2.6-1Fixed in 7.2.7-1

Event History

Apr 24, 2026
CVE Published
via MITRE·02:35 PM
Data Sourced
via MITRE·02:35 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityAffected Software
Apr 26, 2026
Data Sourced
via Microsoft·08:06 AM
DescriptionSeverityWeakness
Sep 21, 2026
Data Sourced
via Launchpad·02:53 PM
Description
Sep 24, 2026
Data Sourced
via Ubuntu·02:55 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·02:56 PM
DescriptionAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Systems using the Linux kernel's SPI DesignWare DMA driver (spi-dw-dma) are the affected population. The issue is triggered in an error path while waiting for an SPI transaction to finish.

2

What level of access does an attacker need?

The supplied CVSS vector indicates local access, low attack complexity, low privileges, and no user interaction. The impact is availability only, with a high availability impact and no stated confidentiality or integrity impact.

3

What happens when the vulnerable error path is reached?

If an error occurs when there is no current SPI message, the driver can attempt to use that missing message while printing an error log. This can cause the system to crash.

4

Is there a workaround if an update cannot be applied immediately?

No workaround is provided in the available data. The described fix changes error logging to use the device from the SPI controller structure rather than relying on a current message.

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