Vulnerability in Kernel package: can: isotp: sanitize CAN ID checks in isotp_bind()

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001909: can: isotp: sanitize CAN ID checks in isotp_bind(). Affects Kernel versions >= e057dd3fc20ffb3d7f150af46542a51b59b90127, < f343dbe82314ab457153c9afd970be4e9e553020. 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 Kernel package is a fundamental component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware, software, and processes. The can-isotp module within the Kernel package is responsible for handling ISO-TP (ISO 15765-2) protocol data units over CAN (Controller Area Network). This protocol is commonly used in automotive and industrial applications for communication between electronic control units (ECUs).

Vulnerability Detail

The vulnerability identified in the can-isotp module involves insufficient sanitization of CAN ID checks in the isotp_bind() function. This vulnerability was introduced in version v5.10 of the Linux Kernel and fixed in version v5.15.33. An attacker could potentially exploit this vulnerability to manipulate or spoof CAN IDs, leading to unauthorized access, data manipulation, or disruption of communication between ECUs. 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

If updating the Kernel package is not immediately feasible, a temporary workaround can be implemented by disabling or restricting access to the affected functionality. This can be achieved by removing or blacklisting the can-isotp module or by applying appropriate access controls at the network or system level. However, it is strongly advised to apply the official fix as soon as possible.

Conclusion

In conclusion, the Kernel package's can-isotp module contains a vulnerability that allows for insufficient sanitization of CAN ID checks in the isotp_bind() function. This vulnerability can potentially be exploited to manipulate or spoof CAN IDs, leading to unauthorized access, data manipulation, or disruption of communication between ECUs. It is crucial to update the Kernel package to version v5.15.33 or later, or apply the recommended workaround, to mitigate the risks associated with this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability could potentially allow an attacker to manipulate or spoof CAN IDs, leading to unauthorized access, data manipulation, or disruption of communication between ECUs.

You can use the Vulert playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert platform will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, no known exploits for this vulnerability have been documented. However, it is important to apply the fix or workaround as soon as possible to mitigate any potential risks.

Yes, this vulnerability can be exploited remotely if the affected functionality is accessible over a network. It is crucial to update the Kernel package or apply the recommended workaround to prevent potential exploitation.

For further support and assistance with vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be happy to assist you in securing your system.

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