CVE-2022-49379 Details
Description
In the Linux kernel, the following vulnerability has been resolved: driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction Mounting NFS rootfs was timing out when deferred_probe_timeout was non-zero [1]. This was because ip_auto_config() initcall times out waiting for the network interfaces to show up when deferred_probe_timeout was non-zero. While ip_auto_config() calls wait_for_device_probe() to make sure any currently running deferred probe work or asynchronous probe finishes, that wasn't sufficient to account for devices being deferred until deferred_probe_timeout. Commit 35a672363ab3 ("driver core: Ensure wait_for_device_probe() waits until the deferred_probe_timeout fires") tried to fix that by making sure wait_for_device_probe() waits for deferred_probe_timeout to expire before returning. However, if wait_for_device_probe() is called from the kernel_init() context: - Before deferred_probe_initcall() [2], it causes the boot process to hang due to a deadlock. - After deferred_probe_initcall() [3], it blocks kernel_init() from continuing till deferred_probe_timeout expires and beats the point of deferred_probe_timeout that's trying to wait for userspace to load modules. Neither of this is good. So revert the changes to wait_for_device_probe(). [1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/ [2] - https://lore.kernel.org/lkml/[email protected]/ [3] - https://lore.kernel.org/lkml/[email protected]/
A vulnerability in the Linux kernel's driver core related to the handling of deferred device probing has been addressed. The issue arose when mounting NFS root filesystems, which timed out due to the deferred_probe_timeout setting. This timeout interfered with the ip_auto_config initialization call, causing delays in network interface availability. The problem was linked to the interaction between the wait_for_device_probe function and the deferred_probe_timeout, leading to either a boot process hang or a blockage of the kernel initialization process. The vulnerability has been resolved by reverting changes that attempted to synchronize the device probing with the timeout, which had inadvertently introduced deadlocks and delays in the boot process.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/29357883a89193863f3cc6a2c5e0b42ceb022761 | kernel.org | Patch |
| https://git.kernel.org/stable/c/4ad6af07efcca85369c21e4897b3020cff2c170b | kernel.org | Patch |
| https://git.kernel.org/stable/c/528229474e1cbb1b3451cb713d94aecb5f6ee264 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5ee76c256e928455212ab759c51d198fedbe7523 | kernel.org | Patch |
| https://git.kernel.org/stable/c/71cbce75031aed26c72c2dc8a83111d181685f1b | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.7.1, < 5.10.122 >= 5.11, < 5.15.47 >= 5.16, < 5.17.15 >= 5.18, < 5.18.4 5.7 - 5.7 rc5 5.7 rc6 5.7 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Sep 22, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |