Vulnerability in driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002962: driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction. Affects Kernel versions >= 35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebe, < 528229474e1cbb1b3451cb713d94aecb5f6ee264. 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 driver core is a fundamental component of the Linux Kernel that manages device drivers. It provides an infrastructure for device discovery, initialization, and management. The driver core is responsible for probing and binding drivers to devices, ensuring proper device initialization and handling. It plays a crucial role in the functioning of the Linux Kernel.

Vulnerability Detail

The vulnerability in the driver core arises from an interaction between the wait_for_device_probe() function and the deferred_probe_timeout mechanism. This vulnerability was introduced in Linux Kernel version v5.7 and has been fixed in version v5.17.15. The exact impact and attack plausibility of this vulnerability have not been proven yet. However, it is important to address this issue to ensure the stability and security of the Linux 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 →

Workaround

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

Conclusion

The vulnerability in the driver core related to the wait_for_device_probe() function and deferred_probe_timeout interaction has been addressed in the Linux Kernel version v5.17.15. It is crucial to update the kernel to this version or later to ensure the security and stability of the Linux Kernel. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The driver core is a fundamental component of the Linux Kernel that manages device drivers. It provides an infrastructure for device discovery, initialization, and management.

The exact impact of this vulnerability is not yet proven. However, it is important to address it to ensure the stability and security of the Linux Kernel.

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

Users can obtain the updated kernel from the official Linux Kernel repository or through their respective Linux distribution's package management system.

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

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