CVE-2026-98615

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

CVSS 0.0 · Non évaluée
Linux•Linux•Versions : <8947f13e436a4ff5eed9f8f019b2865a07af4bb2, 6.14.7, <=6.12.*, 6.18.55, 0, <a969db6548a1b046cd1423701f5f9c3f5794e90d, 6.12.112, fea860a2a6136658708fb530a82d59d29f708b74, <8a052cd4b2caee1f90cf0e3874377066939c90e7, <=6.18.*, 6.12.29, 6.15, <=7.2.*, 7.2.9, 0a4aa8a32ddb96f320173a2e9b0e41f4a6d3746c, <=*, <6.15, <ed4163f6ba9b52bfd6216d5215ee7b8eb5072411, 3b12f00ddd08e888273b2ac0488d396d90a836fc, <6.12.112, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox When tearing down the FW mailbox Rx ring, fbnic_mbx_reset_desc_ring() writes AW_CFG with FLUSH set and everything else, BME included, cleared. Clearing BME halts the device's writes to the host but leaves the staged requests parked in the PUL write pipeline rather than draining them, so on the write path FLUSH alone never terminates the outstanding requests and the flush the firmware waits on never completes. Add the FLUSH_MODE definition and set both bits so the staged writes drain out of the pipeline on their own. BME stays cleared, so nothing lands on the host; it is restored later in fbnic_mbx_init_desc_ring() when the ring is rebuilt, once the outstanding writes are gone. The read path is unaffected. AR_CFG has no equivalent mode bit and AR_FLUSH terminates the outstanding reads by itself, so it is left as is. Both writes remain plain stores rather than read-modify-writes. That is deliberate: the matching write in fbnic_mbx_init_desc_ring() restores BME and the TLP attributes, and clears both flush bits as a side effect.

Gravité et risque d'exploitation

CVE-2026-98615 obtient un score CVSS de 0.0/10, soit une gravité non évaluée.

Que faire ?

  • Vérifiez si Linux (versions <8947f13e436a4ff5eed9f8f019b2865a07af4bb2, 6.14.7, <=6.12.*, 6.18.55, 0, <a969db6548a1b046cd1423701f5f9c3f5794e90d, 6.12.112, fea860a2a6136658708fb530a82d59d29f708b74, <8a052cd4b2caee1f90cf0e3874377066939c90e7, <=6.18.*, 6.12.29, 6.15, <=7.2.*, 7.2.9, 0a4aa8a32ddb96f320173a2e9b0e41f4a6d3746c, <=*, <6.15, <ed4163f6ba9b52bfd6216d5215ee7b8eb5072411, 3b12f00ddd08e888273b2ac0488d396d90a836fc, <6.12.112, 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