CVE-2021-47469: spi: Fix deadlock when adding SPI controllers on SPI buses

Published May 22, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved: spi: Fix deadlock when adding SPI controllers on SPI buses Currently we have a global spiaddlock which we take when adding new devices so that we can check that we're not trying to reuse a chip select that's already controlled. This means that if the SPI device is itself a SPI controller and triggers the instantiation of further SPI devices we trigger a deadlock as we try to register and instantiate those devices while in the process of doing so for the parent controller and hence already holding the global spiaddlock. Since we only care about concurrency within a single SPI bus move the lock to be per controller, avoiding the deadlock. This can be easily triggered in the case of spi-mux.

Other sources

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

— NVD

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Change SPI device-add locking from the global spi_add_lock to a lock scoped per SPI controller, so nested SPI device instantiation on spi-mux does not deadlock.

Event History

May 22, 2024
CVE Published
via MITRE·06:23 AM
Rejected
via MITRE·06:23 AM
Data Sourced
via NVD·07:15 AM
Description
Mar 3, 2025
Rejected
via MITRE·08:16 AM

Frequently Asked Questions

1

What is the severity of CVE-2021-47469?

CVE-2021-47469 is a vulnerability in the Linux kernel that could potentially lead to a deadlock when adding SPI controllers.

2

How do I fix CVE-2021-47469?

To fix CVE-2021-47469, you should upgrade to a patched version of the Linux kernel that resolves this deadlock issue.

3

Which versions of the Linux kernel are affected by CVE-2021-47469?

CVE-2021-47469 affects Linux kernel versions prior to 5.10.230, 5.14.15, and certain 5.15 release candidates.

4

Is CVE-2021-47469 a critical vulnerability?

The criticality of CVE-2021-47469 may depend on the specific system's use case and configuration, but it is important to address it to prevent potential deadlocks.

5

Where can I find more information on CVE-2021-47469?

Detailed information about CVE-2021-47469 can be found in official Linux kernel patches and security advisories.

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