Heimdall Security Logo

CVE-2026-46004

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 7.0.4, <=6.1.*, <=7.0.*, <=6.12.*, <f537e3ad69609f6924a4db6b4a7f6561f5288bdd, 0, 6.18.27, 5.15.209, <b956e48371f2ff72b76be9a829800ecec963bd45, <=5.10.*, <=6.6.*, 6.1.175, <da938aa9fc7826901921dcea225948ab21a97e45, 7.1, <6251e3e256337a30160ef59ab1580dde4d1acd28, <=6.18.*, 2.6.25, 5.10.258, <2.6.25, <09616e25f502080ba684fc7fcf959d1376ab756d, <=*, <e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056, <=5.15.*, <28abd224db4a49560b452115bca3672a20e45b2f, 6.6.140, 6.12.86, <096dd8519cf2f768e9e14f224b627f7aaee1a9c5, 8e3cd08ed8e590952aa9a656758cb24d4ba898f8

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The probe procedure of setup_card() in caiaq driver doesn't treat the error cases gracefully, e.g. the error from snd_card_register() calls snd_card_free() but continues. This would lead to a UAF for the further calls like snd_usb_caiaq_control_init(), as Berk suggested in another patch in the link below. However, the problem is not only that; in general, this function drops the all error handlings (as it's a void function) although its caller can propagate an error to snd_probe(), which eventually calls snd_card_free() as a proper error path. That said, we should treat each error case in setup_card(), and just return the error code promptly, which is then handled later as a fatal error in snd_probe(). This patch achieves it by changing the setup_card() to return an error code. Also, the superfluous snd_card_free() call is removed, too. Note that card->private_free can be set still safely at returning an error. All called functions in card_free() have checks of the unassigned resources or NULL checks.

Gravité et risque d'exploitation

CVE-2026-46004 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.18 %, ce qui la place devant 6.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 7.0.4, <=6.1.*, <=7.0.*, <=6.12.*, <f537e3ad69609f6924a4db6b4a7f6561f5288bdd, 0, 6.18.27, 5.15.209, <b956e48371f2ff72b76be9a829800ecec963bd45, <=5.10.*, <=6.6.*, 6.1.175, <da938aa9fc7826901921dcea225948ab21a97e45, 7.1, <6251e3e256337a30160ef59ab1580dde4d1acd28, <=6.18.*, 2.6.25, 5.10.258, <2.6.25, <09616e25f502080ba684fc7fcf959d1376ab756d, <=*, <e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056, <=5.15.*, <28abd224db4a49560b452115bca3672a20e45b2f, 6.6.140, 6.12.86, <096dd8519cf2f768e9e14f224b627f7aaee1a9c5, 8e3cd08ed8e590952aa9a656758cb24d4ba898f8) 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