extcon: Modify extcon device to be created after driver data is set

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002550: extcon: Modify extcon device to be created after driver data is set. Affects Kernel versions < 033ec4e7e59ae5e1ef1e8c10bc6552926044ed1c. 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 extcon package is a component of the Linux Kernel that handles external connector events. It provides a framework for managing the state of external connectors, such as USB ports or headphone jacks, and notifies the system when a connector is plugged or unplugged. The extcon device is created during the initialization of the extcon driver and is responsible for managing the connection state of the external connectors. However, in versions prior to v5.18.4 of the Linux Kernel, the extcon device was created before the driver data was set, potentially leading to uninitialized data usage or other vulnerabilities.

Vulnerability Detail

The vulnerability in the extcon package arises from the incorrect order of operations during the creation of the extcon device. By creating the device before setting the driver data, uninitialized data may be used, leading to potential security vulnerabilities. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.18.4 by commit 033ec4e7e59ae5e1ef1e8c10bc6552926044ed1c.

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 this vulnerability has been fixed in Linux Kernel version v5.18.4, there is no specific workaround available. It is recommended to update to the fixed version of the kernel.

Conclusion

The extcon package in the Linux Kernel prior to v5.18.4 is vulnerable to a potential security issue where the extcon device is created before the driver data is set. This could result in uninitialized data usage or other vulnerabilities. It is recommended to update to Linux Kernel version v5.18.4 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The extcon package is a component of the Linux Kernel that handles external connector events and manages the state of external connectors.

The extcon device is created during the initialization of the extcon driver and is responsible for managing the connection state of external connectors.

The impact of this vulnerability is not yet proven. However, it could potentially lead to uninitialized data usage or other security vulnerabilities.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.18.4 or later.

As this vulnerability has been fixed in Linux Kernel version v5.18.4, there is no specific workaround available.

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