CVE-2021-47469 Affecting kernel-azure-devel package, versions <5.14.21-150500.33.57.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-KERNELAZUREDEVEL-7252805
  • published14 Jun 2024
  • disclosed13 Jun 2024

Introduced: 13 Jun 2024

CVE-2021-47469  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 kernel-azure-devel to version 5.14.21-150500.33.57.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-azure-devel package and not the kernel-azure-devel package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

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.

CVSS Scores

version 3.1