First published: Wed 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 spi_add_lock 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 spi_add_lock. 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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <5.4.286 | |
Linux Kernel | >=5.5<5.10.230 | |
Linux Kernel | >=5.11<5.14.15 | |
Linux Kernel | =5.15-rc1 | |
Linux Kernel | =5.15-rc2 | |
Linux Kernel | =5.15-rc3 | |
Linux Kernel | =5.15-rc4 | |
Linux Kernel | =5.15-rc5 | |
debian/linux | <=5.10.223-1<=5.10.234-1 | 6.1.123-1 6.1.128-1 6.12.12-1 6.12.16-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-47469 is a vulnerability in the Linux kernel that could potentially lead to a deadlock when adding SPI controllers.
To fix CVE-2021-47469, you should upgrade to a patched version of the Linux kernel that resolves this deadlock issue.
CVE-2021-47469 affects Linux kernel versions prior to 5.10.230, 5.14.15, and certain 5.15 release candidates.
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.
Detailed information about CVE-2021-47469 can be found in official Linux kernel patches and security advisories.