CVE-2022-49379
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-49379
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-49379.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2022-49379
- Downstream
- Related
- Published
- 2025-02-26T02:11:17Z
- Modified
- 2025-10-15T21:37:44.442401Z
- Summary
- driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
driver core: Fix waitfordeviceprobe() & deferredprobe_timeout interaction
Mounting NFS rootfs was timing out when deferredprobetimeout was non-zero [1]. This was because ipautoconfig() initcall times out waiting for the network interfaces to show up when deferredprobetimeout was non-zero. While ipautoconfig() calls waitfordeviceprobe() to make sure any currently running deferred probe work or asynchronous probe finishes, that wasn't sufficient to account for devices being deferred until deferredprobe_timeout.
Commit 35a672363ab3 ("driver core: Ensure waitfordeviceprobe() waits until the deferredprobetimeout fires") tried to fix that by making sure waitfordeviceprobe() waits for deferredprobetimeout to expire before returning.
However, if waitfordeviceprobe() is called from the kernelinit() context:
Before deferredprobeinitcall() [2], it causes the boot process to hang due to a deadlock.
After deferredprobeinitcall() [3], it blocks kernelinit() from continuing till deferredprobetimeout expires and beats the point of deferredprobe_timeout that's trying to wait for userspace to load modules.
Neither of this is good. So revert the changes to waitfordevice_probe().
[1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/ [2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - https://lore.kernel.org/lkml/Yo3WvGnNk3LvLb7R@linutronix.de/
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/29357883a89193863f3cc6a2c5e0b42ceb022761
- https://git.kernel.org/stable/c/4ad6af07efcca85369c21e4897b3020cff2c170b
- https://git.kernel.org/stable/c/528229474e1cbb1b3451cb713d94aecb5f6ee264
- https://git.kernel.org/stable/c/5ee76c256e928455212ab759c51d198fedbe7523
- https://git.kernel.org/stable/c/71cbce75031aed26c72c2dc8a83111d181685f1b
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebeFixed71cbce75031aed26c72c2dc8a83111d181685f1b
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebeFixed29357883a89193863f3cc6a2c5e0b42ceb022761
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebeFixed528229474e1cbb1b3451cb713d94aecb5f6ee264
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebeFixed4ad6af07efcca85369c21e4897b3020cff2c170b
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebeFixed5ee76c256e928455212ab759c51d198fedbe7523