Heimdall Security Logo

CVE-2026-74719

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.6.152, 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44, 0, <5.8, <=7.1.*, 5.15.216, <10cb31b2b74cb664c6c95cf72364d7d5c483ab82, <=5.10.*, <=6.6.*, <e0eb87677c76b157cdf8eb7c1f19e56227165a33, 7.1.9, <06734dfeaeba886aab1bf147249195b888ac3e4d, <976245094925bab9bc39366b2e9ab44ffcde61d0, <a1e980d7a9e7ee6faf4f5fd7b450413b969af26d, 6.1.183, <=6.18.*, 6.12.104, <bfc336a9fbbf09805f3dfe25c195a4db90af2846, <e384f3cba6ea709f5b2272b1770db4ce14047f78, 6.18.45, <=*, <=5.15.*, 5.8, 5.10.265, 7.2, <c23c409228629107203d3c3e95fff1473173f1a6

Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler() The SMC_LLC_CONFIRM_LINK / SMC_LLC_ADD_LINK_CONT branch in smc_llc_event_handler() stores an incoming qentry into the local LLC flow without first checking whether a qentry is already pending. If a malicious or buggy peer sends a second CONFIRM_LINK or ADD_LINK_CONT request while a flow is active and flow->qentry is already set, smc_llc_flow_qentry_set() overwrites the pointer without freeing the previous allocation, leaking one kmalloc-96 object per spurious message. The sibling SMC_LLC_DELETE_LINK branch already has the correct !flow->qentry guard. Apply the same guard to the CONFIRM_LINK/ADD_LINK_CONT branch so that a duplicate message when qentry is already occupied falls through to break and is freed by the kfree(qentry) at the out: label, rather than silently leaking the existing allocation. The response direction (smc_llc_rx_response()) is unaffected: it already guards with flow->qentry at the equivalent site and drops duplicate responses correctly.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.6.152, 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44, 0, <5.8, <=7.1.*, 5.15.216, <10cb31b2b74cb664c6c95cf72364d7d5c483ab82, <=5.10.*, <=6.6.*, <e0eb87677c76b157cdf8eb7c1f19e56227165a33, 7.1.9, <06734dfeaeba886aab1bf147249195b888ac3e4d, <976245094925bab9bc39366b2e9ab44ffcde61d0, <a1e980d7a9e7ee6faf4f5fd7b450413b969af26d, 6.1.183, <=6.18.*, 6.12.104, <bfc336a9fbbf09805f3dfe25c195a4db90af2846, <e384f3cba6ea709f5b2272b1770db4ce14047f78, 6.18.45, <=*, <=5.15.*, 5.8, 5.10.265, 7.2, <c23c409228629107203d3c3e95fff1473173f1a6) 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