Use-after-free vulnerability in spi: stm32 package

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000391: spi: stm32: Fix use-after-free on unbind. Affects Kernel versions >= 0390f6f1d0bcd36d0ab22367498cc2c4619c05d8, < 05b3f9b0ac32fb3714efa13270700868b3000019. 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 Penetration testing for web, API and mobile 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: stm32 package is a component of the Linux Kernel, which is responsible for handling SPI (Serial Peripheral Interface) communication on STM32 microcontrollers. SPI is a synchronous serial communication interface commonly used for connecting microcontrollers to peripheral devices. The spi: stm32 package provides the necessary drivers and functionality for SPI communication on STM32-based systems.

Vulnerability Detail

The use-after-free vulnerability in spi: stm32 occurs when the package fails to properly handle the unbind operation. This can lead to a situation where a reference to a freed memory object is still accessible, potentially allowing an attacker to exploit this situation and execute arbitrary code or cause a denial of service. The vulnerability was introduced in version v5.10.37 of the Linux Kernel and has been fixed in version v5.10.37 by commit 05b3f9b0ac32fb3714efa13270700868b3000019.

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

As a workaround, users can avoid the unbind operation that triggers the use-after-free vulnerability. However, this may not be a feasible solution in all cases, as it may limit the functionality or performance of the spi: stm32 package. It is strongly recommended to apply the fix by updating the Linux Kernel to the patched version.

Conclusion

The use-after-free vulnerability in spi: stm32 can pose a significant security risk, potentially allowing attackers to execute arbitrary code or cause a denial of service. It is crucial to update the Linux Kernel to version v5.10.37 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The spi: stm32 package is a component of the Linux Kernel that provides drivers and functionality for SPI communication on STM32 microcontrollers.

A use-after-free vulnerability occurs when a program continues to use a memory object after it has been freed. This can lead to various security issues, including the execution of arbitrary code or denial of service.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this use-after-free vulnerability in spi: stm32.

Yes, this vulnerability has been fixed in version v5.10.37 of the Linux Kernel by commit 05b3f9b0ac32fb3714efa13270700868b3000019.

To protect your system, it is recommended to update the Linux Kernel to version v5.10.37 or later, which includes the fix for this vulnerability. Follow the provided steps in the 'how_to_fix' section to update your kernel.

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