CVE-2026-90107

Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: free pending qentry in smc_llc_flow_stop() before memset smc_llc_flow_stop() resets a flow struct with a blind memset: spin_lock_bh(&lgr->llc_flow_lock); memset(flow, 0, sizeof(*flow)); flow->type = SMC_LLC_FLOW_NONE; spin_unlock_bh(&lgr->llc_flow_lock); If flow->qentry is non-NULL at this point the pointer is overwritten without the allocation being freed, leaking one kmalloc object. A late-arriving duplicate CONFIRM_LINK or ADD_LINK_CONT message can set flow->qentry after the legitimate message has been consumed by the waiter via smc_llc_flow_qentry_clr() (which NULLs the pointer but leaves flow->type non-zero) but before the flow completes and smc_llc_flow_stop() runs. In that window the duplicate is stashed into flow->qentry, and then lost when smc_llc_flow_stop() zeros the struct. Call smc_llc_flow_qentry_del() inside the lock before the memset. smc_llc_flow_qentry_del() already checks flow->qentry before freeing, so the normal case where no entry is pending is a no-op.

Gravité et risque d'exploitation

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

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 5.15.221, <5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b, 5.10.270, 0, <5.8, 6.1.188, 6.18.52, <8e3deb150a5237b672c4579e69a6deb02027dbed, <=5.10.*, <=6.6.*, 6.6.157, 7.2.6, <957dba2b8b5aebfe09caa6a6b22b958079082eab, 555da9af827d95134656fa459c8f3ece04dd867a, <f03aa5d36ae3c4068a1c3885146be99aa7fd9307, <032aec7d03c9102616b98fea74f8f7145e7f867c, <=6.18.*, <0879ea157acc1ac6752f6fcb755d1f91a2359238, 6.12.110, <=7.2.*, <11bc373ee6630709f0c2da2e7860c23d503c9e9d, <=*, <=5.15.*, 5.8, <5ee0ceddc7785c6dcf4a8107fef01f0414a354f4, 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

• https://git.kernel.org/stable/c/8e3deb150a5237b672c4579e69a6deb02027dbed
• https://git.kernel.org/stable/c/11bc373ee6630709f0c2da2e7860c23d503c9e9d
• https://git.kernel.org/stable/c/032aec7d03c9102616b98fea74f8f7145e7f867c
• https://git.kernel.org/stable/c/957dba2b8b5aebfe09caa6a6b22b958079082eab
• https://git.kernel.org/stable/c/f03aa5d36ae3c4068a1c3885146be99aa7fd9307
• https://git.kernel.org/stable/c/0879ea157acc1ac6752f6fcb755d1f91a2359238
• https://git.kernel.org/stable/c/5ff429dd6725fa6c1e17a4ed0be8ab675f67a98b
• https://git.kernel.org/stable/c/5ee0ceddc7785c6dcf4a8107fef01f0414a354f4