CVE-2026-90220

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 7.1.5, 6.18.40, <=6.12.*, 0527a56cb327021cb73167cfddf0e49efa043500, <6e6e471eef1d5d8cb056c7d364023fe048249204, 0, efc86691e4d8083d9e380ea95042c2cf679f65fd, 6.18.52, 6.12.97, <59e1592d3c270ff4642d5d6dc55c545306eb0693, 7.2.6, <b1e8d40663997aacaa198f37ce6893e07aaba77a, <=6.18.*, <42c3f856d13a91a0d4c302a0c6854813621136db, 6.12.110, <=7.2.*, <6.12.110, <6.18.52, <=*, <7.2, 7.2, 93d260ce43a81df579c98bee92b91316df9c1c57, dae23c545eb5a2be3b27a82fd0f611894fb8ab69, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Don't leak the extension cell pointer in the bounce payload The bounce_error_event() embeds the failed event in the bounce payload by pointing data.ext.ptr at it. When that event is a queued variable-length event, its own data.ext.ptr holds the address of its first extension cell, put there by snd_seq_event_dup(). The payload goes out verbatim through snd_seq_expand_var_event(), so the address reaches userspace. That is the same address commit 705dd6dcbc0e ("ALSA: seq: Clear variable event pointer on read") removed from the event header. The read path still clears it there, just above the call that expands the payload. Embed a sanitised copy instead, treated exactly as snd_seq_read() treats the header. A stack copy is enough because delivery is synchronous and snd_seq_event_dup() copies before returning. An unprivileged client reaches this by setting SNDRV_SEQ_FILTER_BOUNCE, queueing a variable-length event to a port that does not exist and reading the bounce back. Eight bytes on 64-bit, from its own pool.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 7.1.5, 6.18.40, <=6.12.*, 0527a56cb327021cb73167cfddf0e49efa043500, <6e6e471eef1d5d8cb056c7d364023fe048249204, 0, efc86691e4d8083d9e380ea95042c2cf679f65fd, 6.18.52, 6.12.97, <59e1592d3c270ff4642d5d6dc55c545306eb0693, 7.2.6, <b1e8d40663997aacaa198f37ce6893e07aaba77a, <=6.18.*, <42c3f856d13a91a0d4c302a0c6854813621136db, 6.12.110, <=7.2.*, <6.12.110, <6.18.52, <=*, <7.2, 7.2, 93d260ce43a81df579c98bee92b91316df9c1c57, dae23c545eb5a2be3b27a82fd0f611894fb8ab69, 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