Use After Free Vulnerability in pch_can

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1002399: can: pch_can: pch_can_rx_normal: fix use after free. Affects Kernel versions >= b21d18b51b31a24d17f883b678432fbdee3d5675, < affbad02bf80380a7403885b9fe4a1587d1bb4f3. 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 pch_can package is a part of the Linux Kernel ecosystem and is responsible for providing support for the PCH (Platform Controller Hub) CAN (Controller Area Network) controller found in Intel chipsets. It allows communication between various devices connected to the CAN bus. The vulnerability in pch_can arises from a use after free issue in the pch_can_rx_normal function.

Vulnerability Detail

The use after free vulnerability in pch_can_rx_normal function can be exploited by an attacker to execute arbitrary code or cause a denial of service. This vulnerability occurs when the function attempts to access memory that has already been freed, leading to unpredictable behavior and potential security risks. The vulnerability was introduced in version v2.6.37 of the Linux Kernel and has been fixed in version v4.14.258.

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 v4.14.258 or later. This can be done by downloading the latest stable version of the Linux Kernel from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided. It is important to ensure that the updated version is compatible with the specific system configuration.

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

Workaround

There is no specific workaround available for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the latest version.

Conclusion

The use after free vulnerability in pch_can can pose significant security risks, allowing an attacker to execute arbitrary code or cause a denial of service. It is crucial to update the Linux Kernel to the latest version to mitigate these risks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use after free vulnerability in pch_can can allow an attacker to execute arbitrary code or cause a denial of service.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is crucial to update the Linux Kernel to the latest version to prevent any potential remote exploitation.

The recommended solution is to update the Linux Kernel to the latest version. However, if updating is not feasible, you can consider implementing additional security measures such as network segmentation, access controls, and intrusion detection systems to mitigate the risk of exploitation.

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 v4.14.258 or later. This can be done by downloading the latest stable version of the Linux Kernel from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided. It is important to ensure that the updated version is compatible with the specific system configuration.

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.