Skip to content
Heist/ feed
Back to feed
UnratedFix available

driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction

Type: advisorySources: OSV

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/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - https://lore.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.122, 5.15.47, 5.17.15, 5.18.4
CVEs
CVE-2022-49379
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 02:06 UTC · Revision 1

Source evidence

driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction

core-osv · Original source

Published 26 Feb 2025, 02:11 UTC

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/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - https://lore.

osv:CVE-2022-49379

Kernel

Fixed versions: 5.10.122, 5.15.47, 5.17.15, 5.18.4

Complete source record
{
  "id": "8202a57a5813962c6f8729c948dec139a99db42b082c66692256d00eb9e7f190",
  "url": "https://osv.dev/vulnerability/CVE-2022-49379",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction",
    "summary": "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/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - https://lore.",
    "evidence": "osv:CVE-2022-49379",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.10.122",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.47",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.17.15",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.18.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2022-49379",
      "aliases": [
        "CVE-2022-49379"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebe"
                },
                {
                  "fixed": "71cbce75031aed26c72c2dc8a83111d181685f1b"
                },
                {
                  "fixed": "29357883a89193863f3cc6a2c5e0b42ceb022761"
                },
                {
                  "fixed": "528229474e1cbb1b3451cb713d94aecb5f6ee264"
                },
                {
                  "fixed": "4ad6af07efcca85369c21e4897b3020cff2c170b"
                },
                {
                  "fixed": "5ee76c256e928455212ab759c51d198fedbe7523"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49379.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.7.0"
                },
                {
                  "fixed": "5.10.122"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.47"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "5.17.15"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.18.0"
                },
                {
                  "fixed": "5.18.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49379.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:25.303357237Z",
      "provider": "osv",
      "references": [
        "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",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49379.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-49379",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49379.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-49379",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 491778,
  "published_at": "2025-02-26T02:11:17.795+00:00"
}