Heimdall Security Logo

CVE-2026-98314

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 2.6.12, <686c7a6af1eea8d2a919303e4c6bbec3de79dbdc, <8c869d5cf5affb20994bdbb60e7d46d65c91b55f, 0, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <555d168bd98daa46daccc68c908201388c834293, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <0b349249d572633d7c8cdeb917623d1676a2b7c3, 7.2.8, <1e713f9bb2ac583521f06b0eb4e22440b1e3d078, <=6.18.*, 5.15.222, <=7.2.*, <d63f5a9f8121fb43c798056d7dd34c58f47185d7, <27f167e117eca310661fbcbacb352ea08face067, <=*, <=5.15.*, 6.18.54, <e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: set timer->private_data before registering the PCM timer snd_pcm_timer_init() calls snd_device_register() to link the new struct snd_timer into the global timer list while it still carries hw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop), and only afterwards sets timer->private_data = substream. Once the timer is on the list under register_mutex, a concurrent reader can already reach it through the same mutex and invoke these callbacks. /proc/asound/timers does this via c_resolution(), and snd_timer_open()+snd_timer_start() reach start()/stop() the same way. All three dereference timer->private_data, which for this brief window is NULL, giving a NULL-pointer dereference: substream = timer->private_data; return substream->runtime ? ... // substream is NULL Move the private_data/private_free assignment before snd_device_register() so the timer is never visible on the list without its private_data set. On the snd_device_register() failure path, private_free() (snd_pcm_timer_free()) can now run, but it only does substream->timer = NULL, which is already NULL at that point since substream->timer is set to the new timer just once, after a successful registration -- so the failure path stays safe.

Gravité et risque d'exploitation

CVE-2026-98314 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 7.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 2.6.12, <686c7a6af1eea8d2a919303e4c6bbec3de79dbdc, <8c869d5cf5affb20994bdbb60e7d46d65c91b55f, 0, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <555d168bd98daa46daccc68c908201388c834293, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <0b349249d572633d7c8cdeb917623d1676a2b7c3, 7.2.8, <1e713f9bb2ac583521f06b0eb4e22440b1e3d078, <=6.18.*, 5.15.222, <=7.2.*, <d63f5a9f8121fb43c798056d7dd34c58f47185d7, <27f167e117eca310661fbcbacb352ea08face067, <=*, <=5.15.*, 6.18.54, <e1eee8f16628f8b6bcae0a366fd6a2dd65e71edd, 7.3) 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