Heimdall Security Logo

CVE-2022-49379

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=5.17.*, <5ee76c256e928455212ab759c51d198fedbe7523, 0, 5.19, <528229474e1cbb1b3451cb713d94aecb5f6ee264, <29357883a89193863f3cc6a2c5e0b42ceb022761, <5.7, 5.18.4, <=5.10.*, 5.15.47, <4ad6af07efcca85369c21e4897b3020cff2c170b, <71cbce75031aed26c72c2dc8a83111d181685f1b, <=5.18.*, 5.10.122, 5.7, <=*, <=5.15.*, 5.17.15, 35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebe

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/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - https://lore.kernel.org/lkml/Yo3WvGnNk3LvLb7R@linutronix.de/

Gravité et risque d'exploitation

CVE-2022-49379 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.20 %, ce qui la place devant 9.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=5.17.*, <5ee76c256e928455212ab759c51d198fedbe7523, 0, 5.19, <528229474e1cbb1b3451cb713d94aecb5f6ee264, <29357883a89193863f3cc6a2c5e0b42ceb022761, <5.7, 5.18.4, <=5.10.*, 5.15.47, <4ad6af07efcca85369c21e4897b3020cff2c170b, <71cbce75031aed26c72c2dc8a83111d181685f1b, <=5.18.*, 5.10.122, 5.7, <=*, <=5.15.*, 5.17.15, 35a672363ab3e8dfe4ebcadb4dd0b2d06bb85ebe) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE