Heimdall Security Logo

CVE-2026-74549

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, 7.2, <=6.12.*, <513d847f7a95bbdbeaaf55fb942c38992587734f, <1b722740ac5c2b2070f9ba922f4e0f227faf0246, 5.4, 0, <=7.1.*, 5.15.216, 6.12.103, <=5.10.*, <=6.6.*, <0d11b2a10269ace29832f584d207ff3768f79dc5, 6.1.183, <689082a4cb166a7ae9729f7b12339e69fdad6c52, <=6.18.*, <4ad2972ef0e1bd1018ad7a72661a4636ed7daecc, <5.4, <=*, <d0b704e569ac3b8416d8e02270cdc9bf830ed395, <=5.15.*, 7.1.8, 6.18.44, 6.6.151, <25b528816f5d83be5236dc182692369e8c9402b0, <4a77f1d72c6db04cbbfab0250292ac71fdea5f0a, 5.10.265, 29c7cb485b321c024dedc168bcbb04451176b163

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (nct6775-core) Prevent access to unsupported weight registers Sashiko reports: During initialization of the nct6116 chip, the driver sets data->pwm_num to 5. However, it assigns several NCT6106 register arrays (such as NCT6106_REG_WEIGHT_DUTY_STEP, NCT6106_REG_WEIGHT_TEMP_SEL, and NCT6106_REG_WEIGHT_TEMP_*) to data->REG_PWM and data->REG_WEIGHT_TEMP. These arrays only contain 3 elements. In nct6775_update_pwm(), the driver iterates up to data->pwm_num. If data->has_pwm has bits 3 or 4 set (which is structurally possible for nct6116), the loop attempts to read elements at index 3 and 4 from these 3-element arrays. This results in a global out-of-bounds read, which can be caught by KASAN. Furthermore, the driver uses these garbage out-of-bounds values as hardware register addresses for subsequent read and write operations. This leads to invalid hardware register access, potentially causing hardware misconfiguration or system crashes. The underlying problem is that the chip does support up to five fan control channels, but only the first three support weight control. Fix the problem by extending the affected weight register arrays with zeroed fields. The driver uses zeroed register addresses to determine if a register is supported or not, and skips accesses for unsupported registers.

Gravité et risque d'exploitation

CVE-2026-74549 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.2, <=6.12.*, <513d847f7a95bbdbeaaf55fb942c38992587734f, <1b722740ac5c2b2070f9ba922f4e0f227faf0246, 5.4, 0, <=7.1.*, 5.15.216, 6.12.103, <=5.10.*, <=6.6.*, <0d11b2a10269ace29832f584d207ff3768f79dc5, 6.1.183, <689082a4cb166a7ae9729f7b12339e69fdad6c52, <=6.18.*, <4ad2972ef0e1bd1018ad7a72661a4636ed7daecc, <5.4, <=*, <d0b704e569ac3b8416d8e02270cdc9bf830ed395, <=5.15.*, 7.1.8, 6.18.44, 6.6.151, <25b528816f5d83be5236dc182692369e8c9402b0, <4a77f1d72c6db04cbbfab0250292ac71fdea5f0a, 5.10.265, 29c7cb485b321c024dedc168bcbb04451176b163) 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