Use After Free Vulnerability in sja1000 Package

Kernel Updated 02 Oct 2025

Summary

19/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002503: can: sja1000: fix use after free in ems_pcmcia_add_card(). Affects Kernel versions >= fd734c6f25aea4b2b44b045e489aec67b388577e, < 923f4dc5df679f678e121c20bf2fd70f7bf3e288. 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 sja1000 package is a component of the Linux Kernel, which is responsible for handling CAN (Controller Area Network) communication. The sja1000 driver provides support for various CAN controllers, allowing devices to communicate over a CAN bus. This vulnerability specifically affects the ems_pcmcia_add_card() function within the sja1000 package.

Vulnerability Detail

The ems_pcmcia_add_card() function in the sja1000 package suffers from a use after free vulnerability. This vulnerability occurs when the function continues to reference memory after it has been freed, leading to potential memory corruption or crashes. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition.

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 update the Linux Kernel to the fixed version to mitigate the risk.

Conclusion

The use after free vulnerability in the sja1000 package can be mitigated by updating the Linux Kernel to version v5.10.85 or later. It is crucial to apply this update to ensure the security and stability of systems utilizing the sja1000 package. For further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The sja1000 package is a component of the Linux Kernel that provides support for CAN communication.

A use after free vulnerability occurs when a program continues to reference memory after it has been freed, leading to potential memory corruption or crashes.

This vulnerability could 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.85 or later.

No, there is no known workaround for this vulnerability. Updating the Linux Kernel is the recommended solution.

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