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-1000944: spi: bcm2835: Fix out-of-bounds access with more than 4 slaves. Affects Kernel versions >= 571e31fa60b3697d5db26140e16d5c45c51c9815, < 82a8ffba54d31e97582051cb56ba1f988018681e. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The spi: bcm2835 package is a driver for the SPI controller found on Broadcom BCM2835-based systems, such as the Raspberry Pi. It provides functionality for communicating with SPI devices connected to the system. The vulnerability in this package allows for out-of-bounds access when more than 4 slaves are used.

Vulnerability Detail

The vulnerability in spi: bcm2835 arises from an out-of-bounds access issue that occurs when the number of 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 is fixed in version v5.10.44. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.44 or later. This can be done by pulling the latest updates from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their distribution to release an updated kernel package.

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 at the moment.

Conclusion

The out-of-bounds access vulnerability in spi: bcm2835 can lead to memory corruption and potential code execution or denial-of-service attacks. It is recommended to update the Linux Kernel to version v5.10.44 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

spi: bcm2835 is a driver for the SPI controller found on Broadcom BCM2835-based systems, such as the Raspberry Pi. It allows communication with SPI devices connected to the system.

The vulnerability can lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.

To fix this vulnerability, update the Linux Kernel to version v5.10.44 or later.

There is currently no known workaround for this vulnerability.

You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry GSD-2021-1000944.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.44 or later. This can be done by pulling the latest updates from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their distribution to release an updated kernel package.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.