Out-of-Bounds Access Vulnerability in spi: bcm2835

Kernel Updated 02 Oct 2025

Summary

30/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1001017: spi: bcm2835: Fix out-of-bounds access with more than 4 slaves. Affects Kernel versions >= 571e31fa60b3697d5db26140e16d5c45c51c9815, < 01415ff85a24308059e06ca3e97fd7bf75648690. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The spi: bcm2835 package is a component of the Linux Kernel, which is responsible for managing the Serial Peripheral Interface (SPI) on the Broadcom BCM2835 SoC. SPI is a synchronous serial communication interface commonly used for connecting microcontrollers, sensors, and other devices. The bcm2835 driver provides support for SPI communication on the Raspberry Pi platform. However, a vulnerability has been identified in the bcm2835 driver that allows out-of-bounds access when more than 4 slaves are connected.

Vulnerability Detail

The vulnerability in spi: bcm2835 arises from an out-of-bounds access issue that occurs when the number of connected slaves exceeds 4. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition. The vulnerability was introduced in version v5.4 of the Linux Kernel and has been fixed in version v5.12.11. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the fix by updating the Linux Kernel to a version that includes the necessary patch.

Conclusion

The out-of-bounds access vulnerability in spi: bcm2835 can be mitigated by updating the Linux Kernel to version v5.12.11 or later. This will ensure that the necessary fix is applied, preventing potential memory corruption and unauthorized code execution. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

spi: bcm2835 is a driver component of the Linux Kernel that provides support for the Serial Peripheral Interface (SPI) on the Broadcom BCM2835 SoC. It enables communication with SPI devices connected to the system.

An out-of-bounds access vulnerability occurs when a program or driver accesses memory outside the bounds of a defined buffer or array. In the case of spi: bcm2835, this vulnerability allows accessing memory beyond the allocated space when more than 4 SPI slaves are connected.

Exploiting this vulnerability could lead to memory corruption, which may allow an attacker to execute arbitrary code or cause a denial-of-service condition. However, the actual impact and attack plausibility have not been proven yet.

To fix this vulnerability, update the Linux Kernel to version v5.12.11 or later. Obtain the latest kernel source code from the official Linux Kernel repository and compile it for your system. Alternatively, wait for your Linux distribution to release an updated kernel package.

No, there is no known workaround for this vulnerability. It is crucial to apply the fix by updating the Linux Kernel to a version that includes the necessary patch.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback