CVE-2026-31749

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <d07d97ca4f7fac467cdcf4a012690853958b7e89, <101ab946b79ad83b36d5cfd47de587492a80acf0, <=6.1.*, <=6.12.*, 0, 6.6.134, 7.0, <5d8d88c8c0eec230de8f1f60e0920a4337939a88, 2323b276308a5da5774b778f39c7fd94b2a3022a, <=5.10.*, 2.6.30, <=6.6.*, <=6.19.*, <3848ae00b1642e2c98ff8cbfd2d3b38c6f53b5c3, 5.15.203, <a01dd339ea6ac58b0967a50085622a6017351140, <2.6.30, <=6.18.*, 6.12.81, <f517646e008fe99ca1800601cd011b110f8684ae, <933a2d6a95f9bfb203e562c9be1dd990c735535c, <=*, <43c68a2c7cc35b7c2a83c285cb4ad3d472b8caa2, 5.10.253, <=5.15.*, 6.1.168, 6.18.22, 6.19.12

Description

In the Linux kernel, the following vulnerability has been resolved: comedi: ni_atmio16d: Fix invalid clean-up after failed attach If the driver's COMEDI "attach" handler function (`atmio16d_attach()`) returns an error, the COMEDI core will call the driver's "detach" handler function (`atmio16d_detach()`) to clean up. This calls `reset_atmio16d()` unconditionally, but depending on where the error occurred in the attach handler, the device may not have been sufficiently initialized to call `reset_atmio16d()`. It uses `dev->iobase` as the I/O port base address and `dev->private` as the pointer to the COMEDI device's private data structure. `dev->iobase` may still be set to its initial value of 0, which would result in undesired writes to low I/O port addresses. `dev->private` may still be `NULL`, which would result in null pointer dereferences. Fix `atmio16d_detach()` by checking that `dev->private` is valid (non-null) before calling `reset_atmio16d()`. This implies that `dev->iobase` was set correctly since that is set up before `dev->private`.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <d07d97ca4f7fac467cdcf4a012690853958b7e89, <101ab946b79ad83b36d5cfd47de587492a80acf0, <=6.1.*, <=6.12.*, 0, 6.6.134, 7.0, <5d8d88c8c0eec230de8f1f60e0920a4337939a88, 2323b276308a5da5774b778f39c7fd94b2a3022a, <=5.10.*, 2.6.30, <=6.6.*, <=6.19.*, <3848ae00b1642e2c98ff8cbfd2d3b38c6f53b5c3, 5.15.203, <a01dd339ea6ac58b0967a50085622a6017351140, <2.6.30, <=6.18.*, 6.12.81, <f517646e008fe99ca1800601cd011b110f8684ae, <933a2d6a95f9bfb203e562c9be1dd990c735535c, <=*, <43c68a2c7cc35b7c2a83c285cb4ad3d472b8caa2, 5.10.253, <=5.15.*, 6.1.168, 6.18.22, 6.19.12) 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