Heimdall Security Logo

CVE-2026-23237

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <da6e06a5fdbabea3870d18c227734b5dea5b3be6, 5.15.201, 6.12.74, <fe747d7112283f47169e9c16e751179a9b38611e, <=6.12.*, <af673209d43b46257540997aba042b90ef3258c0, 6.1.164, 6.18.13, 0, 529aa8cb0a59367d08883f818e8c47028e819d0d, <=5.10.*, <=6.6.*, <97528b1622b8f129574d29a571c32a3c85eafa3c, <eb214804f03c829decf10998e9b7dd26f4c8ab9e, <2.6.33, 2.6.33, <993708fc18d0d0919db438361b4e8c1f980a8d1b, <=6.18.*, <=*, <=5.15.*, 6.19, <9cf4b9b8ad09d6e05307abc4e951cabdff4be652, 6.6.127, 5.10.251

Description

In the Linux kernel, the following vulnerability has been resolved: platform/x86: classmate-laptop: Add missing NULL pointer checks In a few places in the Classmate laptop driver, code using the accel object may run before that object's address is stored in the driver data of the input device using it. For example, cmpc_accel_sensitivity_store_v4() is the "show" method of cmpc_accel_sensitivity_attr_v4 which is added in cmpc_accel_add_v4(), before calling dev_set_drvdata() for inputdev->dev. If the sysfs attribute is accessed prematurely, the dev_get_drvdata(&inputdev->dev) call in in cmpc_accel_sensitivity_store_v4() returns NULL which leads to a NULL pointer dereference going forward. Moreover, sysfs attributes using the input device are added before initializing that device by cmpc_add_acpi_notify_device() and if one of them is accessed before running that function, a NULL pointer dereference will occur. For example, cmpc_accel_sensitivity_attr_v4 is added before calling cmpc_add_acpi_notify_device() and if it is read prematurely, the dev_get_drvdata(&acpi->dev) call in cmpc_accel_sensitivity_show_v4() returns NULL which leads to a NULL pointer dereference going forward. Fix this by adding NULL pointer checks in all of the relevant places.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <da6e06a5fdbabea3870d18c227734b5dea5b3be6, 5.15.201, 6.12.74, <fe747d7112283f47169e9c16e751179a9b38611e, <=6.12.*, <af673209d43b46257540997aba042b90ef3258c0, 6.1.164, 6.18.13, 0, 529aa8cb0a59367d08883f818e8c47028e819d0d, <=5.10.*, <=6.6.*, <97528b1622b8f129574d29a571c32a3c85eafa3c, <eb214804f03c829decf10998e9b7dd26f4c8ab9e, <2.6.33, 2.6.33, <993708fc18d0d0919db438361b4e8c1f980a8d1b, <=6.18.*, <=*, <=5.15.*, 6.19, <9cf4b9b8ad09d6e05307abc4e951cabdff4be652, 6.6.127, 5.10.251) 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