CVE-2025-40107

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.16.*, 6.17, 0, <fd00cf38fd437c979f0e5905e3ebdfc3f55a4b96, <1d2ef21f02baff0c109ad78b9e835fb4acb14533, <6b696808472197b77b888f50bc789a3bae077743, 6.16.12, 6.12.52, <=6.6.*, <d1fc4c041459e2d4856c1b2501486ba4f0cbf96b, 4.12, 6.6.111, <=*, <4.12, 57e83fb9b7468c75cb65cde1d23043553c346c6d, 6.1.156, <e93af787187e585933570563c643337fa731584a

Description

In the Linux kernel, the following vulnerability has been resolved: can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled This issue is similar to the vulnerability in the `mcp251x` driver, which was fixed in commit 03c427147b2d ("can: mcp251x: fix resume from sleep before interface was brought up"). In the `hi311x` driver, when the device resumes from sleep, the driver schedules `priv->restart_work`. However, if the network interface was not previously enabled, the `priv->wq` (workqueue) is not allocated and initialized, leading to a null pointer dereference. To fix this, we move the allocation and initialization of the workqueue from the `hi3110_open` function to the `hi3110_can_probe` function. This ensures that the workqueue is properly initialized before it is used during device resume. And added logic to destroy the workqueue in the error handling paths of `hi3110_can_probe` and in the `hi3110_can_remove` function to prevent resource leaks.

Gravité et risque d'exploitation

CVE-2025-40107 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.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <=6.16.*, 6.17, 0, <fd00cf38fd437c979f0e5905e3ebdfc3f55a4b96, <1d2ef21f02baff0c109ad78b9e835fb4acb14533, <6b696808472197b77b888f50bc789a3bae077743, 6.16.12, 6.12.52, <=6.6.*, <d1fc4c041459e2d4856c1b2501486ba4f0cbf96b, 4.12, 6.6.111, <=*, <4.12, 57e83fb9b7468c75cb65cde1d23043553c346c6d, 6.1.156, <e93af787187e585933570563c643337fa731584a) 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