Heimdall Security Logo

CVE-2024-38605

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.8 · Élevée
EPSS 0.7%
Linux•Linux•Versions : <=6.1.*, 6.10, 81033c6b584b44514cbb16fffc26ca29a0fa6270, 0, <6b8374ee2cabcf034faa34e69a855dc496a9ec12, <c935e72139e6d523defd60fe875c01eb1f9ea5c5, <e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92, <=5.10.*, <=6.6.*, <e007476725730c1a68387b54b7629486d8a8301e, 6.8.12, <=6.9.*, 5.10.219, 6.6.33, 5.9, 5.15.161, <=6.8.*, <5.9, <e7e0ca200772bdb2fdc6d43d32d341e87a36f811, 6.1.93, <d7ff29a429b56f04783152ad7bbd7233b740e434, <=*, <=5.15.*, 6.9.3, <39381fe7394e5eafac76e7e9367e7351138a29c1

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.

Gravité et risque d'exploitation

CVE-2024-38605 obtient un score CVSS de 8.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.75 %, ce qui la place devant 54.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 6.10, 81033c6b584b44514cbb16fffc26ca29a0fa6270, 0, <6b8374ee2cabcf034faa34e69a855dc496a9ec12, <c935e72139e6d523defd60fe875c01eb1f9ea5c5, <e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92, <=5.10.*, <=6.6.*, <e007476725730c1a68387b54b7629486d8a8301e, 6.8.12, <=6.9.*, 5.10.219, 6.6.33, 5.9, 5.15.161, <=6.8.*, <5.9, <e7e0ca200772bdb2fdc6d43d32d341e87a36f811, 6.1.93, <d7ff29a429b56f04783152ad7bbd7233b740e434, <=*, <=5.15.*, 6.9.3, <39381fe7394e5eafac76e7e9367e7351138a29c1) 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